-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
br: leader selection with tikv store balance score during the ebs data restore #39402
Conversation
…lect leaders focus on a few of store
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-unit-test |
/run-check_dev |
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
@WangLe1321: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
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
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.
rest LGTM
/run-check_dev_2 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 9300b80
|
/run-check_dev_2 |
/run-build |
/run-unit-test |
TiDB MergeCI notify
|
What problem does this PR solve?
balance the region leader selection
Issue Number: close #39404
Problem Summary:
backup cluster without workload. restore flashback has the hot store to handle. root cause is selection leader focus on some tikv.
What is changed and how it works?
flashback using the write key to the region instead of the delete key from RocksDB.
flashback request always sends to a region leader.
ebs restore has the following workflow:
in AWS EBS, disk performance may slow, and sometimes backup happens on a cluster without any workload.
in the above circumstances, in one region, we have some peers have the same logterm, last index and commit index. those peers can be select as a region leader.
this PR to select the best leader for the region.
best
means flashback request can be Evenly distributed all tikvs.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.