retry: make backoff more reasonable for DataNotReady #550
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
Yisaer
approved these changes
Jul 19, 2022
Signed-off-by: nolouch <nolouch@gmail.com>
youjiali1995
approved these changes
Jul 19, 2022
nolouch
added a commit
to nolouch/client-go
that referenced
this pull request
Jul 19, 2022
Signed-off-by: nolouch <nolouch@gmail.com>
disksing
pushed a commit
that referenced
this pull request
Jul 25, 2022
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.
Signed-off-by: nolouch nolouch@gmail.com
Once the
data not readyerror is encountered, it will back off and try the next peer. BTW, most scenarios using stale read are latency sensitive, 100ms is a relatively large value.such as: