Provide an interface to halt all scheduler and checking #6493
Labels
affects-6.5
This bug affects the 6.5.x(LTS) versions.
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
added
component/schedule
ti-chi-bot bot
pushed a commit
that referenced
this issue
May 25, 2023
ref #6493 Add an option to halt the cluster scheduling. Signed-off-by: JmPotato <[email protected]>
HuSharp
added
needs-cherry-pick-release-6.5
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
Jun 6, 2023
ref tikv#6493 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot bot
pushed a commit
that referenced
this issue
Jun 6, 2023
…#6558) ref #6493, ref #6498 Add an option to halt the cluster scheduling. Signed-off-by: husharp <[email protected]> Co-authored-by: husharp <[email protected]>
|
related PR #6569 |
rleungx
pushed a commit
to rleungx/pd
that referenced
this issue
Dec 1, 2023
) ref tikv#6493 Add an option to halt the cluster scheduling. Signed-off-by: JmPotato <[email protected]>
ti-chi-bot bot
added a commit
that referenced
this issue
May 8, 2024
…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 <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ti-chi-bot bot
pushed a commit
that referenced
this issue
May 9, 2024
…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 <[email protected]> Co-authored-by: JmPotato <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
May 20, 2024
ref tikv#6493, close tikv#8095 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot
pushed a commit
to ti-chi-bot/pd
that referenced
this issue
May 20, 2024
ref tikv#6493, close tikv#8095 Signed-off-by: ti-chi-bot <[email protected]>
ti-chi-bot bot
pushed a commit
that referenced
this issue
May 22, 2024
…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 <[email protected]> Co-authored-by: JmPotato <[email protected]> Co-authored-by: lhy1024 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: