region_cache: filter peers on tombstone or dropped stores (#24726)#25838
region_cache: filter peers on tombstone or dropped stores (#24726)#25838ti-srebot wants to merge 1 commit intopingcap:release-5.0from
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
[REVIEW NOTIFICATION] This pull request has not been approved. 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. DetailsReviewer can indicate their review by submitting an approval review. |
|
@ti-srebot: This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved by the collaborators. AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review. DetailsInstructions 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 kubernetes/test-infra repository. |
|
/run-all-tests |
|
@youjiali1995 you're already a collaborator in bot's repo. |
cherry-pick #24726 to release-5.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/25838After apply modifications, you can push your change to this PR via:
Signed-off-by: youjiali1995 zlwgx1023@gmail.com
What problem does this PR solve?
Issue Number: close #24648
Problem Summary:
TiDB doesn't handle tombstone or dropped stores correctly. It may report an error if there is a peer on such a store.
What is changed and how it works?
What's Changed:
tombstonestate which means the store is a tombstone.Region.init().asyncCheckAndResolveLoop()andinitResolve(). Nowunresolvedstores will only be resolved byinitResolve().How it Works:
Check List
Tests
Side effects
Release note