When a node cannot rejoin the HA (Percona XtraDB Cluster - PXC) cluster automatically, an operator needs to manually force a MySQL node to rejoin.
This article describes the case where a single node is joined to a cluster. For bootstrapping, please see the TAS or MySQL tile documentation.
TAS/EAR
If your HA cluster is experiencing downtime or is in a degraded state, VMware Tanzu recommends first running the "mysql-diag" tool to gather information regarding the current state of the cluster. This tool will either report a healthy cluster with (typically) 3 running nodes, a cluster in quorum with two running nodes and a third node needing to re-join, or a cluster that has lost quorum and requires a bootstrap. The "mysql-diag" tool is available on the mysql_monitor instance for a Tanzu Application Service for VMs (TAS) internal cluster or on the mysql_jumpbox instance for a MySQL tile HA service instance
This procedure removes all the data from a server node, forces it to join the cluster, receiving a current copy of the data from one of the other nodes already in the cluster. The steps are slightly different based on which MySQL cluster this is for.
Notes:
- Do not do this if there is any data on the local node that you need to preserve.
- The other two nodes must be online and healthy. You can validate this by looking at the "mysql-diag" output or checking the MySQL Proxy logs (i.e., "grep 'Healthcheck failed on backend' proxy.combined.log"). "mysql-diag" reports a healthy node as "Synced" and "Primary".
For a TAS MySQL cluster or a MySQL tile HAS cluster:
To restart the database on the instance, either: