-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Stop waiting for the ready notification if the server has stopped #16754
base: main
Are you sure you want to change the base?
Conversation
Need to add a test. |
I believe a test case could be added to
The start should fail and |
Signed-off-by: Benjamin Wang <[email protected]>
We shouldn't restart stopped & removed node, but etcd shouldn't hang indefinitely when users call Another case is to only start one node in a 3-node cluster, then the node should be blocked on the <-s.ReadyNotify(), in such case, when users call Close(), it shouldn't be blocked. |
The following is a possible test case that shows that the code change fixes the issue:
I'm not sure why but the "Secure" version of the test does not work while the "Insecure" works just fine. Pretty much the identical code fix and test case also works for 3.5.9. Then only difference is that |
@Hendrik-H Please,
Does it make sense to you? |
The test you suggested (starting only one node of a cluster) is actually a different issue. The
|
new PR is #16758 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Fix #9533
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.