Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Replication controller issues too many lists #6562

Closed
fgrzadkowski opened this issue Apr 8, 2015 · 7 comments
Closed

Replication controller issues too many lists #6562

fgrzadkowski opened this issue Apr 8, 2015 · 7 comments
Assignees
@bprashanth
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
Milestone
v1.0

Comments

@fgrzadkowski
Copy link
Contributor

Currently RC has the following logic:

MainLoop():

  1. Watch for new RC and sync them immediately
  2. Every 5 sec list all RC and sync them

SyncRC():

  1. List all pods matching selector for RC
  2. Add/Remove pods

This is suboptimal on both layers. We should use watch for both RC and pods. Current implementation generates very high load in apiserver.
@fgrzadkowski fgrzadkowski added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. team/master labels Apr 8, 2015
@fgrzadkowski fgrzadkowski self-assigned this Apr 8, 2015
@fgrzadkowski fgrzadkowski added this to the v1.0 milestone Apr 8, 2015
@fgrzadkowski
Copy link
Contributor Author

cc @wojtek-t @davidopp @lavalamp

@fgrzadkowski fgrzadkowski mentioned this issue Apr 8, 2015
Closed
3 tasks
@davidopp
Copy link
Member

davidopp commented Apr 8, 2015

@bprashanth

@bprashanth
Copy link
Contributor

I believe this is addressed in #5884

specifically #5884 (comment)

@wojtek-t wojtek-t mentioned this issue Apr 17, 2015
Closed
@lavalamp lavalamp assigned bprashanth and unassigned fgrzadkowski Apr 27, 2015
@lavalamp
Copy link
Member

Changing assignee since @bprashanth is actually working on this.

@wojtek-t
Copy link
Member

wojtek-t commented May 5, 2015

@fgrzadkowski @bprashanth - what's the current status of it? Is it fixed now?

@fgrzadkowski
Copy link
Contributor Author

I think this is done. Currently most lists come from kubelet which is expected.

@wojtek-t
Copy link
Member

wojtek-t commented May 5, 2015

Thanks for confirmation (that was also my observation).

@wojtek-t wojtek-t closed this as completed May 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bprashanth bprashanth

Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
5 participants
@lavalamp @davidopp @wojtek-t @fgrzadkowski @bprashanth