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.
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
reduce unnecessary tikvServerBusy backoff when able to try next replica #1184
reduce unnecessary tikvServerBusy backoff when able to try next replica #1184
Changes from 16 commits
2a92b1a
6439bf0
d393317
0ffcce3
79ec047
4e5bd12
d6a259a
0dfd389
d7ab10b
5c49640
f8a0b8e
a7fe007
6a3ae20
3cc9eee
eb0f14d
ff2c7d9
5c82a08
6ed4aee
589c2d8
a156b79
c048653
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just do fast retry when
tikv_client_read_timeout
is configured? It looks a little bit dangerous to useas most of the request would be fast retried .
Besides, maybe we could consult slow information to decide whether fast retry should work. /cc @zyguan @MyonKeminta
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the original logic of canFallback2Follower is trying to do fast backoff when retry next replica, so fast backoff is not only work for
tikv_client_read_timeout
is configured.cc @you06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@crazycs520 It the current logic the same? If so we could continue first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic is not same with before, this PR is for the fix issue #1166, and keep some optimization from #990 and #923