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) #4178

Merged

Conversation

HunDunDM
Copy link
Member

This is a 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.

…nds (tikv#4078)

* checker: judging that the peer is down is no longer based on DownSeconds

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

* address comment

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

Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Sep 28, 2021

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • disksing
  • lhy1024

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 do-not-merge/cherry-pick-not-approved release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Sep 28, 2021
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Sep 28, 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 28, 2021
@zhouqiang-cl zhouqiang-cl added the cherry-pick-approved Cherry pick PR approved by release team. label Sep 28, 2021
@HunDunDM
Copy link
Member Author

/rebuild

@codecov
Copy link

codecov bot commented Sep 28, 2021

Codecov Report

Merging #4178 (fe5b3ec) into release-5.1-20210926 (897734a) will increase coverage by 0.04%.
The diff coverage is n/a.

Impacted file tree graph

@@                   Coverage Diff                    @@
##           release-5.1-20210926    #4178      +/-   ##
========================================================
+ Coverage                 75.26%   75.30%   +0.04%     
========================================================
  Files                       245      245              
  Lines                     24863    24859       -4     
========================================================
+ Hits                      18713    18720       +7     
+ Misses                     4523     4518       -5     
+ Partials                   1627     1621       -6     
Flag Coverage Δ
unittests 75.30% <ø> (+0.04%) ⬆️

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%) ⬆️
server/region_syncer/server.go 83.33% <0.00%> (-6.07%) ⬇️
server/tso/allocator_manager.go 78.63% <0.00%> (-1.17%) ⬇️
server/cluster/cluster.go 83.25% <0.00%> (-0.81%) ⬇️
server/core/storage.go 67.68% <0.00%> (-0.77%) ⬇️
server/cluster/coordinator.go 73.34% <0.00%> (-0.71%) ⬇️
client/client.go 71.96% <0.00%> (+0.13%) ⬆️
server/grpc_service.go 48.34% <0.00%> (+0.22%) ⬆️
server/member/member.go 68.81% <0.00%> (+0.53%) ⬆️
... and 9 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 897734a...fe5b3ec. Read the comment docs.

@HunDunDM
Copy link
Member Author

/merge

@ti-chi-bot
Copy link
Member

@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

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

Commit hash: fe5b3ec

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Sep 28, 2021
@ti-chi-bot ti-chi-bot merged commit fb7d2a4 into tikv:release-5.1-20210926 Sep 28, 2021
@HunDunDM HunDunDM deleted the release-5.1-20210926-patch-4078 branch September 28, 2021 15:10
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. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants