-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
store/tikv: limit batch split count for one request (#18191) #18694
store/tikv: limit batch split count for one request (#18191) #18694
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
@Connor1996 please accept the invitation then you can push to the cherry-pick pull requests. |
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.
LGTM
/test |
LGTM |
/merge |
Sorry @XuHuaiyu, you don't have permission to trigger auto merge event on this branch. |
/merge |
/run-all-tests |
cherry-pick #18191 to release-3.0
Signed-off-by: Connor1996 zbk602423539@gmail.com
What problem does this PR solve?
Too much split may cause TiKV latency spike.
What is changed and how it works?
For one batch split request, TiKV will write all newly created regions' metadata into one write batch of RocksDB. So limit the batch split for one request and separate it into multiple requests.
Related changes
Check List
Release note