-
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
statistics: fix the hot region API cannot work without hot scheduler #4424
Conversation
[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. |
Codecov Report
@@ Coverage Diff @@
## master #4424 +/- ##
==========================================
- Coverage 74.96% 74.82% -0.15%
==========================================
Files 277 279 +2
Lines 27627 27627
==========================================
- Hits 20711 20671 -40
- Misses 5082 5106 +24
- Partials 1834 1850 +16
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
06ba0ad
to
7e86154
Compare
7e86154
to
0297d6f
Compare
0297d6f
to
bcd5c4a
Compare
bcd5c4a
to
e73e323
Compare
edd1769
to
1b5a50b
Compare
/run-unit-tests |
The lock problem needs to pay attention to. |
@@ -535,35 +517,33 @@ func (c *coordinator) resetSchedulerMetrics() { | |||
|
|||
func (c *coordinator) collectHotSpotMetrics() { |
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.
There is some difference between collection and GetHotXXXXRegions.
1b5a50b
to
1f1b30d
Compare
/hold cancel |
Signed-off-by: Ryan Leung <rleungx@gmail.com>
cedc96c
to
4222c18
Compare
@@ -1590,23 +1581,17 @@ func (checker *prepareChecker) collect(region *core.RegionInfo) { | |||
|
|||
// GetHotWriteRegions gets hot write regions' info. | |||
func (c *RaftCluster) GetHotWriteRegions(storeIDs ...uint64) *statistics.StoreHotPeersInfos { | |||
c.RLock() |
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.
Do we no longer need locks?
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.
I think so.
Signed-off-by: Ryan Leung <rleungx@gmail.com>
/merge |
@rleungx: 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: 4f68846
|
…ikv#4424) * refacter store load in hot region scheduler ref tikv#3879 Signed-off-by: Ryan Leung <rleungx@gmail.com> * resolve conflicts Signed-off-by: Ryan Leung <rleungx@gmail.com> * fix the hot region API cannot work when hot scheduler is disabled Signed-off-by: Ryan Leung <rleungx@gmail.com> * resolve conflicts Signed-off-by: Ryan Leung <rleungx@gmail.com> * clean up Signed-off-by: Ryan Leung <rleungx@gmail.com> * make drop region atomically Signed-off-by: Ryan Leung <rleungx@gmail.com> * address the comment Signed-off-by: Ryan Leung <rleungx@gmail.com>
/run-cherry-pick |
In response to a cherrypick label: new pull request created to branch |
ref tikv#3879 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
close #3879. But this PR should be reviewed after the following PRs are merged:
What is changed and how it works?
This PR mainly makes the following changes:
hasHotStatus
interfacestatistics
packageCheck List
Tests
Release note