Associate each region with an independent backoffer (#17568) #17584
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
Signed-off-by: sre-bot <[email protected]>
|
/run-all-tests |
sre-bot
added
component/tikv
type/3.1-cherry-pick
type/enhancement
lzmhhh123
added
status/LGT2
zz-jason
added
the
status/can-merge
|
/run-all-tests |
|
@sre-bot merge failed. |
|
/merge |
|
/run-all-tests |
|
@sre-bot merge failed. |
|
/run-all-tests |
|
/merge |
|
/run-all-tests |
|
/merge |
|
Your auto merge job has been accepted, waiting for:
|
|
@sre-bot merge failed. |
|
/run-all-tests |
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.
cherry-pick #17568 to release-3.1
Signed-off-by: Xintao [email protected]
What problem does this PR solve?
Issue Number: close tikv/tikv#7853
Problem Summary:
The backoffer of the boRegionMiss has a backoff mechanism with a starting time of 2ms and a maximum of 500ms. After log verification, a SQL command will share the same backoffer, that is, if multiple regions return epoch not match error, then the backoffer will quickly rise to 500ms. It is easy to exceed the preset time limit of 40s, causing SQL errors on the client.
What is changed and how it works?
What's Changed: Add a function to get Backoffer
How it Works: Use a Map to store backoffer with specific region id
Related changes
Check List
Tests
Before this PR, the SQL usually returns
region is unavailableSide effects
No
Release note
Backofferfor each region to avoid the SQL command timeout issue when multiple region requests fail at the same time