-
Notifications
You must be signed in to change notification settings - Fork 742
scheduler: make hot v2 more suitable small hot region (#6827) #6864
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
scheduler: make hot v2 more suitable small hot region (#6827) #6864
Conversation
close tikv#6645 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[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 submitting an approval review. |
@cfzjywxk Yes, it's a bugfix, I think it's ok to merge to 6.5. |
Signed-off-by: lhy1024 <admin@liudos.us>
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## release-6.5 #6864 +/- ##
===============================================
- Coverage 75.63% 75.58% -0.05%
===============================================
Files 328 328
Lines 33171 33189 +18
===============================================
- Hits 25088 25087 -1
- Misses 5938 5948 +10
- Partials 2145 2154 +9
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
/merge |
@lhy1024: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger
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: 2d55756
|
This is an automated cherry-pick of #6827
What problem does this PR solve?
Issue Number: Close #6645
What is changed and how does it work?
At the master, when the load difference between the high and low nodes is large, the hot peer needs to be larger than 20% of the diff or 2% of the low node.
In this pr, we introduce the 20th node to be compared with 2% of the low node and take the smaller of these values to avoid unscheduling when the load is all composed of small hotspots.
And we cache
filterHotpeers
to avoid redundancy calculations.Check List
Tests
master after evict leader
this pr after evict leader


Release note