-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix for etcd client oneshot cluster member cycling #16307
Fix for etcd client oneshot cluster member cycling #16307
Conversation
/assign @deads2k |
@rrati the pick was clean? |
@deads2k More or less. The changes to the _test file aren't included because this version of etcd didn't have the tests. The changes to the client code applied cleanly. |
lgtm Do you have an issue or bug to tie to this? |
A BZ, but no github issue |
remind me how we're managing picks for non-kube repos? also, an issue to track bumping to a release that includes this would be good (and an issue for kube, which is impacted the same way) |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, rrati The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue |
Do we have a backport of this into origin master? The upstream PR only merged into etcd 3.3+. |
it was backported into etcd 3.2.8 in etcd-io/etcd@15e9510 and picked up in 3.7+ in 6032f62#diff-1c6011bace39f9ad159c10fa9a674a3a |
@liggitt how about 3.2.16 we have in 3.9 ? |
yes, >= 3.2.8 verified this fix is in master: origin/vendor/github.com/coreos/etcd/client/client.go Lines 375 to 398 in 1e041c8
3.9: origin/vendor/github.com/coreos/etcd/client/client.go Lines 375 to 398 in 6d21b7d
3.8: origin/vendor/github.com/coreos/etcd/client/client.go Lines 375 to 398 in ff72b3f
3.7: origin/vendor/github.com/coreos/etcd/client/client.go Lines 375 to 398 in a8deba5
|
@liggitt without any deeper knowledge of the client code: all your references point to the etcd2 client, not the clientv3 package. |
hmm, true. I wonder if there was a similar issue with the etcd v3 client |
But even in v3, there is a 10 second context passed to the dial func. How can that block for 15 minutes? (@mfojtik noticed that) |
With persistent grpc connections we certainly do not talk about a Dial call here. |
Backport of etcd-io/etcd#8519