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

Provide an interface to halt all scheduler and checking #6493

Closed
JmPotato opened this issue May 19, 2023 · 1 comment
Closed

Provide an interface to halt all scheduler and checking #6493

JmPotato opened this issue May 19, 2023 · 1 comment
Labels
affects-6.5 component/schedule Scheduling logic. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. type/development The issue belongs to a development tasks

Comments

@JmPotato
Copy link
Member

Development Task

In some special situations, suspending all scheduling is a very helpful behavior, such as before performing Flashback on the TiKV cluster, so it is best to provide an interface to do this. It should be noted that the suspension of scheduling here is best able to remember and restore the old configuration, rather than simply deleting all schedulers and checkers in a crude manner.
@JmPotato JmPotato added component/schedule Scheduling logic. type/development The issue belongs to a development tasks labels May 19, 2023
@JmPotato JmPotato mentioned this issue May 22, 2023
Merged
ti-chi-bot bot pushed a commit that referenced this issue May 25, 2023
@JmPotato
config, cluster: add an option to halt the cluster scheduling (#6498)
99e2419 
ref #6493

Add an option to halt the cluster scheduling.

Signed-off-by: JmPotato <ghzpotato@gmail.com>
@HuSharp HuSharp added needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. affects-6.5 labels Jun 6, 2023
@ti-chi-bot ti-chi-bot mentioned this issue Jun 6, 2023
Merged
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue Jun 6, 2023
@JmPotato @ti-chi-bot
This is an automated cherry-pick of tikv#6498
3ccbba6 
ref tikv#6493

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot bot pushed a commit that referenced this issue Jun 6, 2023
@ti-chi-bot @HuSharp
config, cluster: add an option to halt the cluster scheduling (#6498) (…
410b176 
…#6558)

ref #6493, ref #6498

Add an option to halt the cluster scheduling.

Signed-off-by: husharp <jinhao.hu@pingcap.com>

Co-authored-by: husharp <jinhao.hu@pingcap.com>
@HuSharp
Copy link
Member

HuSharp commented Jun 16, 2023

related PR #6569

@HuSharp HuSharp closed this as completed Jun 16, 2023
rleungx pushed a commit to rleungx/pd that referenced this issue Dec 1, 2023
@JmPotato @rleungx
config, cluster: add an option to halt the cluster scheduling (tikv#6498
fbdddff 
)

ref tikv#6493

Add an option to halt the cluster scheduling.

Signed-off-by: JmPotato <ghzpotato@gmail.com>
@JmPotato JmPotato mentioned this issue May 7, 2024
Merged
ti-chi-bot bot added a commit that referenced this issue May 8, 2024
@JmPotato @ti-chi-bot
*: individually check the scheduling halt for online unsafe recovery (#…
740f15e 
…8147)

ref #6493, close #8095

Individually check the scheduling halt for online unsafe recovery to avoid unexpectedly persisting the halt option in the intermediate process.

Signed-off-by: JmPotato <ghzpotato@gmail.com>

Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
@ti-chi-bot ti-chi-bot mentioned this issue May 8, 2024
Merged
ti-chi-bot bot pushed a commit that referenced this issue May 9, 2024
@ti-chi-bot @JmPotato
*: individually check the scheduling halt for online unsafe recovery (#…
fca469c 
…8147) (#8155)

ref #6493, close #8095

Individually check the scheduling halt for online unsafe recovery to avoid unexpectedly persisting the halt option in the intermediate process.

Signed-off-by: JmPotato <ghzpotato@gmail.com>

Co-authored-by: JmPotato <ghzpotato@gmail.com>
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue May 20, 2024
@JmPotato @ti-chi-bot
This is an automated cherry-pick of tikv#8147
c86fcfb 
ref tikv#6493, close tikv#8095

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue May 20, 2024
Closed
ti-chi-bot pushed a commit to ti-chi-bot/pd that referenced this issue May 20, 2024
@JmPotato @ti-chi-bot
This is an automated cherry-pick of tikv#8147
9d2a577 
ref tikv#6493, close tikv#8095

Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot mentioned this issue May 20, 2024
Merged
ti-chi-bot bot pushed a commit that referenced this issue May 22, 2024
@ti-chi-bot @JmPotato @lhy1024
*: individually check the scheduling halt for online unsafe recovery (#…
cfc10f5 
…8147) (#8194)

ref #6493, close #8095

Individually check the scheduling halt for online unsafe recovery to avoid unexpectedly persisting the halt option in the intermediate process.

Signed-off-by: JmPotato <ghzpotato@gmail.com>

Co-authored-by: JmPotato <ghzpotato@gmail.com>
Co-authored-by: lhy1024 <liuhanyang@pingcap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-6.5 component/schedule Scheduling logic. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. type/development The issue belongs to a development tasks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JmPotato @HuSharp