1) systemd was unaware of the true state of the mysqld daemon.
stop and then start restored the unit
2) corosync though spewing log entries about mysql being down did not remove the mysql/2 unit from the cluster
Doing some loop testing to try and re-create the problem.
Two problems were found:
1) systemd was unaware of the true state of the mysqld daemon.
stop and then start restored the unit
2) corosync though spewing log entries about mysql being down did not remove the mysql/2 unit from the cluster
Doing some loop testing to try and re-create the problem.