-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Bump kubernetes-client to 3.1.10 #271
Conversation
The command execution in v3 is a lot slower than in v2, all the times I've tried there is a consistent gap of 30 seconds where nothing happens
|
There is a wait of 30 seconds somewhere
Up to 5 threads in the testCommandExecution is fine, over that there is the 30 seconds wait. Some threads may finish in a second, rest will finish after the 30 secs |
@carlossg: OOTB the client supprts up to 5 concurrent requests per host (see 1). This is actually passed to okhttp and I am not quite sure how it handles it internally, but it does look very suspicious. Can you try increasin that number and see if that makes any difference? Also, I think that its essential to merge this: #239 as it will dramatically reduce the number of requests. |
Actually this test broke between kubernetes-client 2.6.2 and 2.6.3 #239 did not solve it |
Minimal test from jenkinsci/kubernetes-plugin#271
Minimal test from jenkinsci/kubernetes-plugin#271
The changes in PR fabric8io/kubernetes-client#855 broke the test, from v2.6.3 to v3.1.6 (included). Threads would hang forever on waitUntilReady In 3.1.7+ the problem is different, it will eventually succeed, but with 30 second pauses I've filed fabric8io/kubernetes-client#997 |
Waiting for a release > 3.1.8 with fabric8io/kubernetes-client@83eda0c |
No description provided.