-
Notifications
You must be signed in to change notification settings - Fork 489
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
PD automatic failover #57
Comments
I am working hard on the feature. I encountered an issue during test verification: PD's I will change the pd podManagementPolicy to |
Another issue: when failover with current pd start script, the ordinal 0 pd will start as a new pd cluster, because it will start with Solution: Change the pd Add an annotation key
Modify the pd start script
|
zh: add supplementary notes in restore
* Update backup-to-s3.md * en: add IAM ENV for S3 backup and restore * update from #57 * Apply suggestions from code review Co-Authored-By: Lilian Lee <lilin@pingcap.com> Co-authored-by: Lilian Lee <lilin@pingcap.com>
When a PD peer is not health for a while (this can be obtained from PD Cluster's
/pd/health
API), operator should:deleteMember
api to delete this member from the pd clusterpart of #47
The text was updated successfully, but these errors were encountered: