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

schedulers: rollback the scheduler when failing to persist (#3787) #3825

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #3787

What problem does this PR solve?

Try to fix #2572.

What is changed and how it works?

This PR corrects the status code and rollback the scheduler when failing to persist.

Check List

Tests

  • Unit test

Related changes

  • Need to cherry-pick to the release branch

Release note

Fix the issue that the scheduler may appear again even if we have already executed the delete operation

@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved labels Jun 30, 2021
@ti-chi-bot ti-chi-bot added component/scheduler Scheduler logic. type/cherry-pick-for-release-4.0 The PR belongs to release-4.0 cherry pick. labels Jun 30, 2021
@zhouqiang-cl zhouqiang-cl added backport-4.0.14 cherry-pick-approved Cherry pick PR approved by release team. labels Jul 6, 2021
@codecov
Copy link

codecov bot commented Jul 6, 2021

Codecov Report

Merging #3825 (18513e8) into release-4.0 (cd9d32c) will increase coverage by 0.11%.
The diff coverage is 68.62%.

Impacted file tree graph

@@               Coverage Diff               @@
##           release-4.0    #3825      +/-   ##
===============================================
+ Coverage        74.75%   74.86%   +0.11%     
===============================================
  Files              211      211              
  Lines            19961    19994      +33     
===============================================
+ Hits             14922    14969      +47     
+ Misses            3701     3695       -6     
+ Partials          1338     1330       -8     
Flag Coverage Δ
unittests 74.86% <68.62%> (+0.11%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
server/api/scheduler.go 37.71% <42.85%> (+0.63%) ⬆️
server/schedulers/grant_leader.go 66.28% <50.00%> (-1.64%) ⬇️
server/cluster/coordinator.go 68.09% <66.66%> (+0.71%) ⬆️
server/schedulers/evict_leader.go 74.00% <88.88%> (+5.86%) ⬆️
server/config/persist_options.go 87.68% <100.00%> (+0.51%) ⬆️
server/id/id.go 76.19% <0.00%> (-4.77%) ⬇️
server/tso/tso.go 80.43% <0.00%> (-2.18%) ⬇️
server/server.go 74.27% <0.00%> (-0.98%) ⬇️
server/grpc_service.go 59.87% <0.00%> (+0.40%) ⬆️
... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd9d32c...18513e8. Read the comment docs.

@rleungx rleungx force-pushed the cherry-pick-3787-to-release-4.0 branch from 517c3c3 to 2ec32eb Compare July 6, 2021 09:34
Signed-off-by: Ryan Leung <rleungx@gmail.com>
@rleungx rleungx force-pushed the cherry-pick-3787-to-release-4.0 branch from 2ec32eb to 768e970 Compare July 6, 2021 09:36
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Jul 6, 2021
Copy link
Contributor

@nolouch nolouch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ti-chi-bot
Copy link
Member Author

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • HunDunDM
  • nolouch

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.

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jul 6, 2021
@nolouch
Copy link
Contributor

nolouch commented Jul 6, 2021

/merge

@ti-chi-bot
Copy link
Member Author

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

/run-all-tests

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 Author

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

Commit hash: 768e970

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jul 6, 2021
@ti-chi-bot ti-chi-bot merged commit 09a7830 into tikv:release-4.0 Jul 6, 2021
@HunDunDM HunDunDM added this to the v4.0.14 milestone Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-approved Cherry pick PR approved by release team. component/scheduler Scheduler logic. release-note Denotes a PR that will be considered when it comes time to generate release notes. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-4.0 The PR belongs to release-4.0 cherry pick.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants