region_cache: filter peers on tombstone or dropped stores (#24726) #25838
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 #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/25838
After 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:
tombstone
state which means the store is a tombstone.Region.init()
.asyncCheckAndResolveLoop()
andinitResolve()
. Nowunresolved
stores will only be resolved byinitResolve()
.How it Works:
Check List
Tests
Side effects
Release note