-
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
store/tikv: fix misuse of PD client's GetStore #23695
Conversation
Signed-off-by: longfangsong <longfangsong@icloud.com>
/cc @youjiali1995 |
Signed-off-by: longfangsong <longfangsong@icloud.com> (cherry picked from commit 630d390e5c414b92d749b8df7e470c6b21310f4e)
Seems the root cause of #22907 is not this PR. Nevertheless, this PR fixes some problems. |
Signed-off-by: longfangsong <longfangsong@icloud.com>
Signed-off-by: longfangsong <longfangsong@icloud.com>
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
@MyonKeminta: Please use If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 1. 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. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: ac0a96e
|
Should we pick this fix to 5.0? |
@zhangjinpeng1987 No. Even though TiDB wrongly uses it, TiDB works well with no issues. |
/run-cherry-picker |
cherry pick to release-4.0 in PR #24498 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-3.0 in PR #24499 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.0 in PR #24500 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com> Signed-off-by: youjiali1995 <zlwgx1023@gmail.com>
Signed-off-by: longfangsong longfangsong@icloud.com
What problem does this PR solve?
Issue Number: close #23676
Problem Summary:
GetStore()
, which may result in dead loops.store.State
isn't changed if it becomes a tombstoneWhat is changed and how it works?
What's Changed:
Skip the early-return
if
branch when "load Store from PD success but pd didn't found the store"How it Works:
By checking the error message. This is a quick and dirty solution. A better solution (which needs to change the pdClient, and maybe the whole way of our error handling process) needs more discussion.
Related changes
Needs to cherry-pick to 5.0.
Check List
Tests
Release note