-
Notifications
You must be signed in to change notification settings - Fork 727
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: region should splitted if region is too hot. #6618
Conversation
Signed-off-by: bufferflies <[email protected]>
Signed-off-by: bufferflies <[email protected]>
[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. |
// regionIsTooHot returns true if any dim of the hot region is greater than the store threshold. | ||
func regionIsTooHot(store *statistics.StoreLoadDetail, region *statistics.HotPeerStat) bool { | ||
return slice.AnyOf(store.LoadPred.Current.Loads, func(i int) bool { | ||
return region.Loads[i] > store.LoadPred.Current.Loads[i]*0.3 |
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.
add const regionTooHotThreshold = 0.3
?
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.
good suggestion, fixed
Signed-off-by: bufferflies <[email protected]>
Can u paste a picture to show |
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. Do we need some manual test?
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.
ci failed
Signed-off-by: bufferflies <[email protected]>
0afad4a
to
25b0145
Compare
yes, I have upload the manual test result. |
Signed-off-by: bufferflies <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #6618 +/- ##
==========================================
+ Coverage 74.17% 74.18% +0.01%
==========================================
Files 413 411 -2
Lines 43349 43067 -282
==========================================
- Hits 32155 31951 -204
+ Misses 8312 8247 -65
+ Partials 2882 2869 -13
Flags with carried forward coverage won't be shown. Click here to find out more. |
/release |
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.
If workload is append write, split is not helpful
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
/hold |
Signed-off-by: bufferflies <[email protected]>
Signed-off-by: bufferflies <[email protected]>
Signed-off-by: bufferflies <[email protected]>
Signed-off-by: bufferflies <[email protected]>
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, but ci failed
Signed-off-by: bufferflies <[email protected]>
Signed-off-by: bufferflies <[email protected]>
Signed-off-by: bufferflies <[email protected]>
57f720f
to
1305bd3
Compare
/merge |
@bufferflies: 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: 1305bd3
|
close tikv#6619 Signed-off-by: bufferflies <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
What problem does this PR solve?
Issue Number: Close #6619
What is changed and how does it work?
Check List
Tests
Code changes
Side effects
Related changes
Release note