-
Notifications
You must be signed in to change notification settings - Fork 719
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
Reduce the impact of etcd leader on the availability of PD leader #7499
Labels
type/enhancement
The issue or PR belongs to an enhancement.
Comments
ti-chi-bot bot
pushed a commit
that referenced
this issue
Jan 17, 2024
ref #7499 Refine the etcd client healthy checker code. Signed-off-by: JmPotato <ghzpotato@gmail.com>
This was referenced Jan 18, 2024
ti-chi-bot bot
pushed a commit
that referenced
this issue
Feb 2, 2024
ref #7499 member: reset campaign times after successful resign Signed-off-by: husharp <jinhao.hu@pingcap.com>
Close with #7737. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have met several cases showing that even if the PD leader can no longer provide services, the etcd leader does not switch, resulting in the entire cluster being unable to provide services and affecting the high availability of PD, ref #7251, pingcap/tidb#48204 and pingcap/tidb#48206.
Because our implementation adopts the design of a PD leader elected based on the etcd leader, we need to determine more clearly whether the current unavailable scenario requires switching the etcd leader rather than just the PD leader to achieve the higher availability.
The text was updated successfully, but these errors were encountered: