-
Notifications
You must be signed in to change notification settings - Fork 720
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
cluster: save to the region cache when pending-peers or down-peers change #3462
Conversation
…ange Signed-off-by: HunDunDM <hundundm@gmail.com>
Signed-off-by: HunDunDM <hundundm@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #3462 +/- ##
==========================================
+ Coverage 74.90% 74.98% +0.08%
==========================================
Files 244 244
Lines 23559 23578 +19
==========================================
+ Hits 17646 17680 +34
+ Misses 4322 4315 -7
+ Partials 1591 1583 -8
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
if len(region.GetDownPeers()) > 0 || len(region.GetPendingPeers()) > 0 { | ||
saveCache = true | ||
if !core.SortedPeersStatsEqual(region.GetDownPeers(), origin.GetDownPeers()) { | ||
log.Debug("down-peers changed", zap.Uint64("region-id", region.GetID())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about printing the difference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally, I think pending is more common, so I used the Debug
level.
[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. Reviewer can indicate their review by writing |
/merge |
@lhy1024: 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. |
This pull request has been accepted and is ready to merge. Commit hash: e23b725
|
/run-all-tests |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-3.0 in PR #3470 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #3471 |
What problem does this PR solve?
close #3456
What is changed and how it works?
Check List
Tests
Related changes
Release note