Consider store status for running operators
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 783
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 36
Description
## Feature Request
### Describe your feature request related problem
In specific cases, such as when the state of the store changes to `Down` and it becomes practically impossible for some operator to continue advancing, the best way is to immediately cancel the operator and free up the quota for other schedulers.
We have previously fixed partial of the issue https://github.com/tikv/pd/pull/4223
The reason for not fixing it completely is that the previous PR only considered `TransferLeader`, `AddLearner`, `AddPeer`. For the other types, it is more complicated to determine if the scheduling could continue. For example, for `PromoteLearner` (located in a down store), if there is only one voter, it cannot continue, if there are more voters, then it can continue.
### Describe the feature you'd like
Consider store status more completely.
### Describe alternatives you've considered
### Teachability, Documentation, Adoption, Migration Strategy
Contributor guide
Assessment
This issue has not been assessed yet.