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

checker: judging that the peer is down is no longer based on DownSeconds (#4078) #4083

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #4078

Signed-off-by: HunDunDM hundundm@gmail.com

What problem does this PR solve?

Fix #4077

After #3462, DownSeconds no longer update with the heartbeat. It will cause the down-peer to not be repaired in time.

What is changed and how it works?

Judging that the peer is down is no longer based on DownSeconds.

Check List

Tests

  • Unit test

Code changes

Side effects

  • Breaking backward compatibility
    • PD judge that the peer is down is no longer based on DownSeconds. In extreme cases, down-peers that would not have been processed will be fixed.

Related changes

  • Need to cherry-pick to the release branch

Release note

Fix the bug that PD would not fix down-peer in time.

Signed-off-by: HunDunDM <hundundm@gmail.com>
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Sep 6, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • disksing
  • 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 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 Sep 6, 2021
@ti-chi-bot ti-chi-bot added component/checker Checker logic. type/bugfix This PR fixes a bug. type/cherry-pick-for-release-5.1 The PR belongs to release-5.1 cherry pick. labels Sep 6, 2021
@codecov
Copy link

codecov bot commented Sep 6, 2021

Codecov Report

Merging #4083 (8372f9d) into release-5.1 (14c12cd) will increase coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@               Coverage Diff               @@
##           release-5.1    #4083      +/-   ##
===============================================
+ Coverage        75.03%   75.04%   +0.01%     
===============================================
  Files              245      245              
  Lines            24558    24554       -4     
===============================================
  Hits             18426    18426              
+ Misses            4513     4508       -5     
- Partials          1619     1620       +1     
Flag Coverage Δ
unittests 75.04% <ø> (+0.01%) ⬆️

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

Impacted Files Coverage Δ
server/schedule/checker/replica_checker.go 71.11% <ø> (+1.03%) ⬆️
server/schedule/checker/rule_checker.go 81.00% <ø> (+0.89%) ⬆️
pkg/tempurl/tempurl.go 45.00% <0.00%> (-25.00%) ⬇️
server/tso/local_allocator.go 80.55% <0.00%> (-9.73%) ⬇️
pkg/dashboard/adapter/manager.go 78.72% <0.00%> (-4.26%) ⬇️
server/tso/tso.go 70.78% <0.00%> (-2.25%) ⬇️
server/tso/allocator_manager.go 76.96% <0.00%> (-1.51%) ⬇️
server/server.go 71.62% <0.00%> (-0.61%) ⬇️
server/cluster/cluster.go 82.88% <0.00%> (-0.36%) ⬇️
server/id/id.go 80.95% <0.00%> (ø)
... and 8 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 14c12cd...8372f9d. Read the comment docs.

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 6, 2021
@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 Sep 9, 2021
@zhouqiang-cl zhouqiang-cl added the cherry-pick-approved Cherry pick PR approved by release team. label Sep 13, 2021
@HunDunDM
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member Author

@HunDunDM: 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: 8372f9d

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Sep 13, 2021
@ti-chi-bot ti-chi-bot merged commit b7968b1 into tikv:release-5.1 Sep 13, 2021
@zhouqiang-cl zhouqiang-cl added this to the v5.1.2 milestone Sep 18, 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/checker Checker 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/bugfix This PR fixes a bug. type/cherry-pick-for-release-5.1 The PR belongs to release-5.1 cherry pick.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants