bitpoke / mysql-operator

Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator.
https://www.bitpoke.io/docs/mysql-operator/getting-started/
Apache License 2.0
993 stars 275 forks source link

[Feature Request] the lost instance auto re-join to cluster after failover #897

Open drivebyer opened 11 months ago

drivebyer commented 11 months ago

Assuming we have a MySQL cluster with 2 nodes. When the source node in the cluster fails, the operator will promote the replica to become the new source node and use a service to provide external access. At this point, there will be only one node in the cluster, and the previous source node will be left disconnected from the cluster. If the node in the cluster also fails at this time, the MySQL cluster will no longer be able to provide external services.

I suggest adding an optional feature, which, when enabled, allows us to reintegrate the disconnected node back into the cluster.