Some weeks ago I had to migrate some independent MySQL servers (some standard MySQL masters, and some just standalone) to a Percona XtraDB Cluster of 3 nodes.
So the easiest way would be to configure each node to become also an asynchronous slave of one of the production servers.
Like illustrated here:
But in this case there was one major issue, the tables where MyISAM and this is not really recommended with Galera replication even if it’s now supported.
Preparing the slaves would then become a loop:
for each production server restoring the dump on the node that will be the dedicated slave convert the table in InnoDB configure and start the replication finally perform SST on the other nodes....
So in this case that should have be done 3 times… that could take some time ! And then, if the single production servers where more than 3 ?
So I decided to use a wonderful feature of MariaDB 10: Multi-source replication.
MariaDB’s multi-source-replication doesn’t have any conflict resolution. The assumption is that there are no conflicts in data between the different masters. Which is the case here, all standalone servers handle different schemas.
I configured the MariaDB server to be slave of all production servers, changed the table engine to InnoDB on it and chose one node of the PXC to be the async slave of that MariaDB server. It worked like a charm and the migration of production to Percona XtraDB Cluster became very easy.
Thank you MariaDB’s team for this feature.
When a sever (a node) is member of a Percona XtraDB Cluster is also standard slave (standard asynchronous replication of MySQL), it can spread in the cluster all statements received from the master if log_slave_updates is enabled.