-
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
scheduler: there is error not handled in evict-leader-scheduler #8619
Comments
Because the code doesn't handle the errors returned by pd/server/schedulers/evict_leader.go Line 393 in d6751dd
Suppose the parameters used to create the evict-leader-scheduler are incorrect or not parsed. In that case, there may be an inconsistency between the in-memory state and the persistence state, resulting in pd not being able to add the evict-leader-scheduler correctly. It can be reproduced by unit test v6.5.10...rleungx:evict-leader
|
/report customer |
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
ref #8619 Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ref tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
ref tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
ref tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
ref tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
ref tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
ref tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close #8619 Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: Ryan Leung <[email protected]>
close #8619 Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: Ryan Leung <[email protected]>
close #8619 Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: Ryan Leung <[email protected]> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
close #8619 Signed-off-by: ti-chi-bot <[email protected]> Signed-off-by: Ryan Leung <[email protected]> Co-authored-by: Ryan Leung <[email protected]>
close tikv#8619 Signed-off-by: ti-chi-bot <[email protected]>
Bug Report
What did you do?
add an evict-leader-scheduler with error params
What did you expect to see?
report an error and it should be successful next time when I use the correct params
What did you see instead?
it failed again when I used correct params
it shows
Failed! [500] "[PD:core:ErrPauseLeaderTransfer]store 75 is paused for leader transfer"
What version of PD are you using (
pd-server -V
)?v6.5.10
The text was updated successfully, but these errors were encountered: