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

'kubectl stop rc' cleanup time taking >> then before. #5655

Closed
timothysc opened this issue Mar 19, 2015 · 2 comments
Closed

'kubectl stop rc' cleanup time taking >> then before. #5655

timothysc opened this issue Mar 19, 2015 · 2 comments
Assignees
@bprashanth
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone
v1.0

Comments

@timothysc
Copy link
Member

Running the same test listed in #5650 shows that the cleanup time now appears to take orders of magnitude longer then before. It used to take ~1 minute for the same test, now takes >> 5+ Minutes to clean the cluster.

kubectl get pods shows all clear but a pdsh docker ps on the cluster shows pods running for an extended length of time.
@cjcullen cjcullen added priority/backlog Higher priority than priority/awaiting-more-evidence. team/cluster labels Mar 19, 2015
@roberthbailey roberthbailey added this to the v1.0 milestone Mar 19, 2015
@bprashanth
Copy link
Contributor

Previously we leaked pods in some cases by deleting the rc instead of calling stop. The delete was quick.
#5745 should give us the ability to watch for 0 replicas in stop, instead of polling.

The docker ps issue might be unrelated as the rc will claim victory if the pods are dead (there's typically some delay, but it won't wait on containers or anything).

@bprashanth bprashanth self-assigned this Mar 23, 2015
@bprashanth bprashanth mentioned this issue Mar 23, 2015
Closed
@brendandburns
Copy link
Contributor

Closing this issue, as I think that the new delay is WAI, and the scheduler throughput stuff is captured elswhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bprashanth bprashanth

Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
v1.0
Development

No branches or pull requests
6 participants
@timothysc @brendandburns @cjcullen @roberthbailey @davidopp @bprashanth