I’m seeing a lot of tutorials that claim I have to pick just one of the nodes in my master-master replicated PXC to act as master for an async slave using vanilla mysql replication, and if something goes wrong it’s “easy to change the master to one of the other nodes.” That’s all well and good, but I don’t want to be the one answering the pager at 2 a.m. to do a simple CHANGE MASTER TO because one of my nodes went down. Ideally the point of an HA cluster is that all but one node can go down and all dependents are none the wiser.
It occurred to me that with GTID replication I might be able to get away with vanilla mysql multi-source replication, simply listing each node in the master-master PXC as a master to the async slave. They all replicate the same gtid’s, which would be idempotent on duplicate updates to the slave, right? Would that work?
Or: is there a better way?
