-
Notifications
You must be signed in to change notification settings - Fork 726
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
config: add hot region history configurations #4019
Conversation
…onfg Signed-off-by: qidi1 <1083369179@qq.com>
[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. |
conf/simconfig.toml
Outdated
@@ -29,3 +29,6 @@ leader-schedule-limit = 32 | |||
region-schedule-limit = 128 | |||
replica-schedule-limit = 32 | |||
merge-schedule-limit = 32 | |||
## TODO:Find a better place to put this config |
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.
Seem we don't need to add these configurations here.
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.
Yes, we can remove it in simconfig.
HotRegionsWriteInterval typeutil.Duration `toml:"hot-regions-write-interval" json:"hot-regions-write-interval"` | ||
|
||
// The day of hot regions data to be reserved.0 means close | ||
HotRegionsResevervedDays int64 `toml:"hot-regions-reserved-days" json:"hot-regions-reserved-days"` |
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.
Why not use typeutil.Duration
?
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.
The unit of this is days, does toml support days?
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.
So, the minimum time of reserving the hot regions is 1 day?
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.
yes,the minimum time of reserving the hot regions is 1 day
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.
What if we just want to keep the history for several hours?
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.
we delete history hot region every 24 hours,if we want reserve several hours,we must change delete function
Signed-off-by: qidi1 <1083369179@qq.com>
Codecov Report
@@ Coverage Diff @@
## master #4019 +/- ##
==========================================
- Coverage 74.53% 74.53% -0.01%
==========================================
Files 258 258
Lines 26075 26079 +4
==========================================
+ Hits 19436 19438 +2
- Misses 4901 4902 +1
- Partials 1738 1739 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Signed-off-by: qidi1 <1083369179@qq.com>
Signed-off-by: qidi1 <1083369179@qq.com>
Signed-off-by: qidi1 <1083369179@qq.com>
Signed-off-by: qidi1 <1083369179@qq.com>
/merge |
@nolouch: 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: d42ac6f
|
* config:add hot_regions_write_interval&hot_regions_remian_days in to confg Signed-off-by: qidi1 <1083369179@qq.com> * change config part Signed-off-by: qidi1 <1083369179@qq.com> * config:merge from remote Signed-off-by: qidi1 <1083369179@qq.com> * config:remove old code Signed-off-by: qidi1 <1083369179@qq.com> * config:change discprtion Signed-off-by: qidi1 <1083369179@qq.com> * config:change default Signed-off-by: qidi1 <1083369179@qq.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
…onfg
Signed-off-by: qidi1 1083369179@qq.com
What problem does this PR solve?
origin pr is here #3989
This PR is oversize and splited into three small one:
#4019
#4020
#4021
Proposal: pingcap/tidb#27487
Associated PR:tikv/tidb#27224
Associated Issue: pingcap/tidb#25281
pingcap/tidb#27373
pingcap/tidb#27374
pingcap/tidb#27374
What is changed and how it works?
add config for hot_region_storage,add hot_regions_write_interval&hot_regions_remian_days in to config
Check List
Tests
Code changes
Side effects
Related changes
pingcap/docs
/pingcap/docs-cn
:pingcap/tidb-ansible
:Release note