BR: Fix stuck when many missing-peer regions in cluster #28497
Merged
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
|
[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. |
ti-chi-bot
added
release-note
YuJuncen
changed the title
kennytm
reviewed
Oct 3, 2021
ti-chi-bot
added
status/LGT2
|
/merge |
|
This pull request has been accepted and is ready to merge. Commit hash: 53fa6ac
|
ti-chi-bot
added
the
status/can-merge
|
/run-cherry-picker |
ti-srebot
pushed a commit
to ti-srebot/tidb
that referenced
this pull request
Oct 9, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
4 tasks
|
cherry pick to release-5.2 in PR #28680 |
ti-chi-bot
pushed a commit
that referenced
this pull request
Oct 13, 2021
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.
What problem does this PR solve?
Issue Number: close #27534
Problem Summary:
Even BR would skip when store count less than max-replica, the replica requirement via placement rules is still possible to make the restore stuck.
What is changed and how it works?
What's Changed:
"Parallel" all scatter request... (No many goroutines spawned, see the code)
How it Works:
So it wouldn't be stuck.
Check List
Tests
Release note