-
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
tikv: drop store's regions when resolve store with tombstone status (#22909) #23071
tikv: drop store's regions when resolve store with tombstone status (#22909) #23071
Conversation
Signed-off-by: ti-srebot <[email protected]>
/run-all-tests |
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
@lysu you're already a collaborator in bot's repo. |
/LGTM |
PTAL @coocood |
/lgtm |
[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 writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 4533f5c
|
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. 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. |
cherry-pick #22909 to release-4.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/23071
After apply modifications, you can push your change to this PR via:
Signed-off-by: lysu [email protected]
What problem does this PR solve?
Issue Number: close #22907
Problem Summary:
old store id can get old tombstone store, so never have chance to refresh region peer to point to new store id
so request will block forever in old store with EpochNotMatchError
What is changed and how it works?
What's Changed:
drop region cache when resolve store but it's tombstone status
How it Works:
after it, retry will re-fetch new region info from PD which point to new store id..
so continue request will got to new store and never block
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note