mysql> SHOW VARIABLES LIKE ‘%version%’;
±------------------------±------------------------------------------------------------------------------------------------+
| Variable_name | Value |
±------------------------±------------------------------------------------------------------------------------------------+
| innodb_version | 5.7.22-22 |
| protocol_version | 10 |
| slave_type_conversions | |
| tls_version | TLSv1,TLSv1.1,TLSv1.2 |
| version | 5.7.22-22-57-log |
| version_comment | Percona XtraDB Cluster (GPL), Release rel22, Revision da86071, WSREP version 29.26, wsrep_29.26 |
| version_compile_machine | x86_64 |
| version_compile_os | debian-linux-gnu |
| version_suffix | -57-log |
±------------------------±------------------------------------------------------------------------------------------------+
9 rows in set (0.01 sec)
I am running a three node cluster. Everything is working great, but for some reason, I cannot get my cluster to come back online after rebooting the cluster stack of three servers.
I followed this article:
and was able to bring up the cluster after doining a killall -9 mysqld on all of my nodes, came right back up just as it should.
When I reboot my cluster, I can go to my primary node (what I call primary), bootstrap it (/etc/init.d/mysql restart-bootstrap) then start all other nodes and everything comes up fine.
I guess my question is simple - how to I make sure the cluster comes back online unattended after a cluster reboot?
Many Thanks