raftstore: mark peer as pending remove after destroying it (#7492) #7836
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
Signed-off-by: 5kbpers <tangminghua@pingcap.com>
|
/run-all-tests |
sre-bot
added
sig/raft
sre-bot
requested review from
BusyJay,
gengliqi,
hicqu,
MyonKeminta and
overvenus
BusyJay
approved these changes
May 14, 2020
gengliqi
approved these changes
May 14, 2020
|
/merge |
sre-bot
added
the
status/can-merge
|
/run-all-tests |
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.
cherry-pick #7492 to release-4.0
Signed-off-by: 5kbpers tangminghua@pingcap.com
What problem does this PR solve?
Problem Summary:
If a peer was destroyed, the subsequent proposals should be neglected.
What is changed and how it works?
What's Changed:
Mark peer as
pending_removeafter destroying it.Related changes
Check List
Release note