raftstore: Make unsafe recovery wait apply cover snapshot apply cases ref #10483#12308
raftstore: Make unsafe recovery wait apply cover snapshot apply cases ref #10483#12308ti-chi-bot merged 16 commits intotikv:masterfrom
Conversation
|
[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. DetailsReviewer can indicate their review by submitting an approval review. |
|
/assign @Connor1996 |
|
/CC @BusyJay |
ec99f00 to
a60f19a
Compare
…0483 Signed-off-by: v01dstar <yang.zhang@pingcap.com>
|
/test |
|
/merge |
|
@Connor1996: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. DetailsInstructions 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. |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 0f1c747 |
|
/test |
7 similar comments
|
/test |
|
/test |
|
/test |
|
/test |
|
/test |
|
/test |
|
/test |
|
|
previous failure isn't due to |
Signed-off-by: v01dstar <yang.zhang@pingcap.com>
I suspect that the test failed due to insufficient wait for the raft log GC, thus the snapshot path was not triggered at all. Added some new code to coordinate the data insertion and raft log GC, hope this can make the test bit more stable. |
|
/merge |
|
@Connor1996: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. DetailsInstructions 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. |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: fedc098 |
… ref tikv#10483 (tikv#12308) ref tikv#10483 Signed-off-by: v01dstar <yang.zhang@pingcap.com>
… ref tikv#10483 (tikv#12308) ref tikv#10483 Signed-off-by: v01dstar <yang.zhang@pingcap.com>
* raftstore: Introduce force leader state (tikv#11932) close tikv#6107, ref tikv#10483 Signed-off-by: Connor1996 <zbk602423539@gmail.com> * raftstore: Wait ticks for hibernated peer when doing force leader (tikv#12364) ref tikv#10483 Force leader is rejected on a peer who is already a leader. For the hibernated leader, it doesn't step down to follower when quorum is missing due to not ticking election. So wait ticks in force leader process for hibernated peers to make sure election ticking is performed. Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io> * raftstore: Make unsafe recovery wait apply cover snapshot apply cases ref tikv#10483 (tikv#12308) ref tikv#10483 Signed-off-by: v01dstar <yang.zhang@pingcap.com> * raftstore: Execute recovery plan via raft (tikv#12022) Signed-off-by: Connor1996 <zbk602423539@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io> Co-authored-by: Yang Zhang <yang.zhang@pingcap.com>
Signed-off-by: v01dstar yang.zhang@pingcap.com
What is changed and how it works?
Issue Number: ref #10483
What's Changed:
Raft snapshot apply has a different code path to update the apply index, compare to other types of Raft entry which update apply index in
raftstore/store/fsm/peer.rs:on_apply_res(). This path was not covered in the initial implementation of "unsafe recovery wait apply", and this PR fixes it.Related changes
PR that adds the initial implementation of unsafe recovery wait apply: #11716
Check List
Tests
Side effects
N/A
Release note