store/tikv: pre-split regions during 2PC to avoid hotspot (#16920) #16959
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
|
/run-all-tests |
sre-bot
added
type/4.0-cherry-pick
type/enhancement
|
/run-integration-copr-test |
|
/rebuild |
|
/merge |
sre-bot
added
the
status/can-merge
|
Your auto merge job has been accepted, waiting for:
|
|
/run-all-tests |
|
@sre-bot merge failed. |
|
/merge |
|
/run-all-tests |
|
@sre-bot merge failed. |
|
/merge |
|
/run-all-tests |
|
@sre-bot merge failed. |
|
/run-integration-copr-test |
|
/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 #16920 to release-4.0
What problem does this PR solve?
Issue Number: close #16573
Problem Summary:
Pre-split region before it become a writing hotspot to avoid the TiKV 'server is busy' error.
What is changed and how it works?
What's Changed:
Pre-split the region during 2PC if we detect there are many mutations into one region.
How it Works:
Call the
store.SplitRegionsandstore.WaitScatterRegionFinishAPI.Related changes
Check List
Tests
http://172.16.4.61:13000/d/000000011/test-cluster-tidb?orgId=1&from=1588073060157&to=1588082547757
Release note
During the two phase commit process, if there are a lot of mutations within a single region, pre-split that region to avoid hotspot.