-
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: fix panic in RegionStore.accessStore (#20204) #20210
Conversation
/run-all-tests |
LGTM |
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
@bobotu, @ti-srebot, @coocood, @lzmhhh123, PTAL. |
1 similar comment
@bobotu, @ti-srebot, @coocood, @lzmhhh123, PTAL. |
@bobotu, @ti-srebot, @coocood, PTAL. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@lysu merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
/run-all-tests |
cherry-pick #20204 to release-4.0
What problem does this PR solve?
Issue Number: close #20181
Problem Summary:
see more in this comments #20181 (comment)
What is changed and how it works?
What's Changed, How it Works:
detect meta.Peer length change after sent fail, we can directly retry if length not match, because it must be another load or refill new cache info, we are no need to reload or change workIdx at this time
Related changes
Check List
Tests
Side effects
Release note
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)