-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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 ectd client and fix initializing IP/Port allocators when etcd is not reachable #9862
Conversation
GCE e2e build/test failed for commit cee8c22ea2d794c42a3e369756c1a3d97a0b43c0. |
As discussed offline - it seems that the Jenkins failure is exactly the reproduction of the problem. |
I don't know where it should be put and whether it's related, but it would be very helpful if while using --etcd-config (go-etcd) flag it would output any errors to kube-apiserver, because for now - if it fails - no logs are being shown. |
@k8s-bot test this please |
GCE e2e build/test failed for commit cee8c22ea2d794c42a3e369756c1a3d97a0b43c0. |
@k8s-bot test this please |
GCE e2e build/test failed for commit cee8c22ea2d794c42a3e369756c1a3d97a0b43c0. |
cee8c22
to
b677cef
Compare
@k8s-bot test this please |
GCE e2e build/test failed for commit b677cef5030af461fd26544748817e352b38adf9. |
b677cef
to
985cb1c
Compare
GCE e2e build/test failed for commit 985cb1cb5450f3c4c0ccb619fd8924a4bd8193a2. |
985cb1c
to
cbe7207
Compare
GCE e2e build/test failed for commit cbe7207bf59d860161b3ee611e9a679c42bf47a4. |
@k8s-bot test this please |
GCE e2e build/test failed for commit cbe7207bf59d860161b3ee611e9a679c42bf47a4. |
GCE e2e build/test failed for commit 333c40b2b15e95333de5f74054eea4f4e2528365. |
333c40b
to
c2bf8f5
Compare
GCE e2e build/test failed for commit c2bf8f5abe8f5c51701becc47c75b3dc018504d3. |
c2bf8f5
to
b703252
Compare
GCE e2e build/test passed for commit b7032521728b4c2d28ad36d546a74812899cc923. |
@k8s-bot test this please |
GCE e2e build/test passed for commit b7032521728b4c2d28ad36d546a74812899cc923. |
b703252
to
d06461f
Compare
This is ready for review. Assigning to @smarterclayton since one of the commits fixes a bug in allocator code. |
GCE e2e build/test passed for commit d06461f119904efb4be7aae5573a7bba043d41cf. |
@davidopp
This is way better (~25%) than the usual run for density test. |
d06461f
to
6ecba7b
Compare
GCE e2e build/test passed for commit 6ecba7b364d385f4d6f5e71de79cb75aecc53fed. |
Shippable complains about @smarterclayton I can't find any of your comments (even those I've already addressed). Is there anything else I should fix with this PR? It'd be great to have it merged today. |
Had one comment that got last. |
6ecba7b
to
4c0c7dd
Compare
LGTM but I'm not sure what the shippable failure is. |
GCE e2e build/test passed for commit 4c0c7dd. |
Issue? Risk level? Milestone? Does it need to be merged anyway? |
@satnam6502 This fixes #9444 and will improve performance by reducing cpu usage on master machine. Based on discussion with @davidopp we want to merge this change before v1.0. I'd say that risk is medium-high due to multiple changes in etcd client library since our last update. I've run e2e tests multiple times (using jenkins and locally) and it looks good. |
Bump ectd client and fix initializing IP/Port allocators when etcd is not reachable
Thanks for merging. I think this merits being included in 1.0 since it substantially improves performance. |
See #10146. There is quite possibly a bug in this PR - it appears to be causing recovery after an etcd failure not to work reliably. |
This PR reintroduces newer version of go-etcd client library (reverted in #9447). It also adds additional debugging to service allocator code to help debug potential failures that I was not able to reproduce locally.
@wojtek-t @smarterclayton
@saad-ali (currentl oncall)
NOTE 1: If you see other places where logging might be useful please add a comment.
NOTE 2: Please do not merge this PR. I will do this tomorrow morning so that I can closely watch jenkins and revert it once I gather more data for debugging.