kubectl get minions takes a long time to output #3938
Comments
|
See #2973 which reports some progress here. |
satnam6502
added
sig/scalability
|
@satnam6502 I have 12 minions that I am trying to list. I was able to list 20ish very quickly but after removing the first node, I noticed the time increase. |
|
Yes, well, I've been trying to list 1,000 minions. Imagine how miserable that is. I am going to ask @davidopp to take a look (or to forward this to someone else.) |
|
Didn't we already cache all minions? Maybe we are not if it only happens after you take down a node. I believe it will be fixed by #3733. Can you verify it once that is in? |
|
#3733 appears merged. You'll need to upgrade to a more recent version of kubernetes for your cluster. |
|
I'm still having problems listing minions. #4078 |
|
#4078 is likely a different issue from this one. |
|
Agreed. On Tue, Feb 3, 2015 at 6:23 PM, Deyuan Deng notifications@github.com
|
I noticed this behavior after I began removing old nodes from a v0.8.2 cluster using kubectl v0.9.1.
After running a
kubectl get minions, the command will hang for quite some time ( haven't timed it yet) but will eventually spit back the current nodes in the cluster. Other kubectl commands seem to work as the should (get service/rc/pod, etc) it just seems to be the get minions that has problems.I'm not sure what to make of this or how to fix. Thanks!
The text was updated successfully, but these errors were encountered: