Skip to content
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

raftstore: only persist merge target if the merge is known to be succeeded #12251

Merged
merged 6 commits into from
Mar 25, 2022

Conversation

NingLin-P
Copy link
Member

What is changed and how it works?

Issue Number: Close #12232

What's Changed:

When destroying, only persist merge target if the merge is known to be succeeded

raftstore: only persist merge target if the merge is known to be succeeded

Check List

Tests

  • Integration test

Release note

fix tikv panic and peer unexpected destroy due to fake merge target

Signed-off-by: linning <linningde25@gmail.com>
Signed-off-by: linning <linningde25@gmail.com>
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Mar 23, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • 5kbpers
  • you06

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

Signed-off-by: linning <linningde25@gmail.com>
tests/failpoints/cases/test_merge.rs Outdated Show resolved Hide resolved
tests/failpoints/cases/test_merge.rs Outdated Show resolved Hide resolved
components/raftstore/src/store/peer.rs Outdated Show resolved Hide resolved
Signed-off-by: linning <linningde25@gmail.com>
@ti-chi-bot ti-chi-bot added the status/LGT1 Status: PR - There is already 1 approval label Mar 25, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Status: PR - There are already 2 approvals and removed status/LGT1 Status: PR - There is already 1 approval labels Mar 25, 2022
@5kbpers
Copy link
Member

5kbpers commented Mar 25, 2022

/merge

@ti-chi-bot
Copy link
Member

@5kbpers: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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.

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: e049c24

@ti-chi-bot ti-chi-bot added the status/can-merge Status: Can merge to base branch label Mar 25, 2022
@you06
Copy link
Contributor

you06 commented Mar 25, 2022

/test

1 similar comment
@you06
Copy link
Contributor

you06 commented Mar 25, 2022

/test

@ti-chi-bot ti-chi-bot merged commit 3364702 into tikv:master Mar 25, 2022
ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 25, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@NingLin-P NingLin-P added the needs-cherry-pick-release-5.4 Type: Need cherry pick to release-5.4 label Mar 28, 2022
ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-3.1 in PR #12290

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.0 in PR #12291

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-3.0 in PR #12292

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.1 in PR #12293

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-4.0 in PR #12294

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.4 in PR #12295

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.3 in PR #12296

ti-srebot pushed a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.2 in PR #12297

NingLin-P added a commit to ti-srebot/tikv that referenced this pull request Mar 28, 2022
Signed-off-by: linning <linningde25@gmail.com>
NingLin-P added a commit to ti-srebot/tikv that referenced this pull request Mar 29, 2022
Signed-off-by: linning <linningde25@gmail.com>
ti-chi-bot added a commit that referenced this pull request Apr 12, 2022
…eeded (#12251) (#12297)

close #12232, ref #12251

raftstore: only persist merge target if the merge is known to be succeeded

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
Signed-off-by: linning <linningde25@gmail.com>

Co-authored-by: NingLin-P <linningde25@gmail.com>
Co-authored-by: linning <linningde25@gmail.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot added a commit that referenced this pull request Apr 24, 2022
…eeded (#12251) (#12295)

close #12232, ref #12251

raftstore: only persist merge target if the merge is known to be succeeded

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
Signed-off-by: linning <linningde25@gmail.com>

Co-authored-by: NingLin-P <linningde25@gmail.com>
Co-authored-by: linning <linningde25@gmail.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ti-chi-bot added a commit that referenced this pull request Jun 15, 2022
…eeded (#12251) (#12296)

close #12232, ref #12251

raftstore: only persist merge target if the merge is known to be succeeded

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
Signed-off-by: linning <linningde25@gmail.com>

Co-authored-by: NingLin-P <linningde25@gmail.com>
Co-authored-by: linning <linningde25@gmail.com>
Co-authored-by: glorv <glorvs@163.com>
Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-3.0 Type: Need cherry pick to release 3.0 needs-cherry-pick-release-3.1 Type: Need cherry pick to release 3.1 needs-cherry-pick-release-4.0 Type: Need cherry pick to release 4.0 needs-cherry-pick-release-5.0 Type: Need cherry pick to release 5.0 needs-cherry-pick-release-5.1 Type: Need cherry pick to release 5.1 needs-cherry-pick-release-5.2 Type: Need cherry pick to release-5.2 needs-cherry-pick-release-5.3 Type: Need cherry pick to release-5.3 needs-cherry-pick-release-5.4 Type: Need cherry pick to release-5.4 needs-cherry-pick-release-6.0 release-note size/L status/can-merge Status: Can merge to base branch status/LGT2 Status: PR - There are already 2 approvals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tikv panic:peer id increased after region is merged, message peer id 2228, local peer id 1140, region id: 649
6 participants