tikv: fix panic in RegionStore.accessStore #20204
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/run-all-tests |
|
/run-check_dev_2 |
|
/run-unit-test |
|
Do we need to recover the panic of |
|
LGTM |
ti-srebot
added
status/LGT2
ti-srebot
approved these changes
Sep 25, 2020
|
/merge |
ti-srebot
added
the
status/can-merge
|
/run-all-tests |
|
/run-all-tests |
|
@lysu merge failed. |
|
/run-check_dev_2 |
|
cherry pick to release-4.0 failed |
|
/run-cherry-picker |
|
cherry pick to release-4.0 failed |
ti-srebot
pushed a commit
that referenced
this pull request
Oct 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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