client: Work around tight loop when retrying watch connection. #9614
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fasaxc
force-pushed
the
work-around-tight-loop
branch
from
57409d0
to
77c80d3
Compare
Add a 100ms sleep to avoid tight loop if reconnection fails quickly. Fixes etcd-io#9578
fasaxc
force-pushed
the
work-around-tight-loop
branch
from
77c80d3
to
710bf4e
Compare
|
Any news on this one? |
|
@fasaxc @caseydavenport This should be addressed by #9840. And was backported and released with 3.2 and 3.3 patch releases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a 100ms sleep to avoid tight loop if reconnection fails quickly.
Fixes #9578