Skip to content
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.

Sign up for GitHub

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

Jump to bottom

scheduler: make evict-slow-trend scheduler more stable and easy to use. #7156

Open
LykxSassinator opened this issue Sep 26, 2023 · 0 comments
Open

scheduler: make evict-slow-trend scheduler more stable and easy to use. #7156

LykxSassinator opened this issue Sep 26, 2023 · 0 comments
Labels
type/enhancement The issue belongs to an enhancement.

Comments

@LykxSassinator
Copy link
Contributor

Enhancement Task

This is a long-term issue to track the development on optimizing evict-slow-trend scheduler and making it easier to use.
@LykxSassinator LykxSassinator added the type/enhancement The issue belongs to an enhancement. label Sep 26, 2023
@LykxSassinator LykxSassinator mentioned this issue Sep 26, 2023
Merged
ti-chi-bot bot pushed a commit that referenced this issue Oct 12, 2023
@LykxSassinator
scheduler: make evict-slow-trend scheduler can manually modify reco…
0adb86f 
…very duration. (#7132)

ref #7156, ref tikv/tikv#15271

With this pr, users can manually modify the minimal recovery time when encountering an I/O jitter case.

That is, only when the jitter is disappear and the recovery time reach this limit, 
can the given slow node be mark with normal for balancing leaders to it.

Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
@LykxSassinator LykxSassinator mentioned this issue Oct 18, 2023
Merged
ti-chi-bot bot added a commit that referenced this issue Oct 19, 2023
@LykxSassinator @ti-chi-bot
schedulers: transplant the recovery-duration setting to `evict-slow…
d9dbf77 
…-store` scheduler. (#7225)

ref #7156

This pr is used to transplant the `recovery-duration` imported in `evict-slow-trend`
scheduler into `evict-slow-store` scheduler. 

It's useful and necessary for users who wanna use `evict-slow-score` scheduler
before we GA `evict-slow-trend` scheduler.

Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
@LykxSassinator LykxSassinator mentioned this issue Nov 7, 2023
Merged
ti-chi-bot bot added a commit that referenced this issue Nov 10, 2023
@LykxSassinator @ti-chi-bot
scheduler: refine the interval of scheduling tick in evict-slow-trend…
b5119ea 
…-scheduler. (#7326)

ref #7156

Implement the `GetNextInterval` for `evict-slow-trend-scheduler`, to refine the ticking interval.

Default `GetNextInterval` is not appropriate for `evict-slow-trend-scheduler`, as it might delay
the checking of other nodes' slowness status.

This pr adjusts the ticking interval of the evict-slow-trend-scheduler to optimize
its behavior. If a slow node is already identified as a candidate, the next
interval is now set to be shorter, ensuring quicker subsequent scheduling. 
This refinement aims to decrease response time.

Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
@niubell niubell mentioned this issue Nov 15, 2023
Merged
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement The issue belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LykxSassinator