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.

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

schedule exit too slow when PD leader changed #4146

Closed
bufferflies opened this issue Sep 23, 2021 · 1 comment · Fixed by #4148
Closed

schedule exit too slow when PD leader changed #4146

bufferflies opened this issue Sep 23, 2021 · 1 comment · Fixed by #4148
Assignees
Labels
severity/major status/TODO The issue will be done in the future. type/bug The issue is confirmed as a bug.

Comments

@bufferflies
Copy link
Contributor

bufferflies commented Sep 23, 2021

Bug Report

What did you do?

I find PD leader exit slow when I transfer leader

[2021/09/23 11:20:25.797 +08:00] [INFO] [leader.go:489] ["leader is deleted"]
[2021/09/23 11:20:25.800 +08:00] [ERROR] [client.go:172] ["region sync with leader meet error"] [error="[PD:grpc:ErrGRPCRecv]rpc error: code = Canceled desc = context canceled"]
[2021/09/23 11:20:26.800 +08:00] [INFO] [server.go:1099] ["leader changed, try to campaign leader"]
[2021/09/23 11:34:12.902 +08:00] [INFO] [coordinator.go:654] ["scheduler has been stopped"] [scheduler-name=balance-region-scheduler] [error="context canceled"]
[2021/09/23 11:34:12.902 +08:00] [INFO] [cluster.go:328] ["coordinator has been stopped"]

What did you expect to see?

I want that all scheduler exit cost less than 2min after leader changed.

What did you see instead?

What version of PD are you using (pd-server -V)?

master

@bufferflies bufferflies added the type/bug The issue is confirmed as a bug. label Sep 23, 2021
@bufferflies bufferflies self-assigned this Sep 23, 2021
@mayjiang0203
Copy link

/severity Major
/assign @bufferflies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major status/TODO The issue will be done in the future. type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants