- 2.4.1 Configuring Multi-Source Replication
- 2.4.2 Provisioning a Multi-Source Replication Slave for GTID-Based Replication
- 2.4.3 Adding GTID-Based Masters to a Multi-Source Replication Slave
- 2.4.4 Adding Binary Log Based Replication Masters to a Multi-Source Replication Slave
- 2.4.5 Starting Multi-Source Replication Slaves
- 2.4.6 Stopping Multi-Source Replication Slaves
- 2.4.7 Resetting Multi-Source Replication Slaves
- 2.4.8 Monitoring Multi-Source Replication
MySQL multi-source replication enables a replication slave to receive transactions from multiple immediate masters in parallel. Multi-source replication can be used to back up multiple servers to a single server, to merge table shards, and consolidate data from multiple servers to a single server. Multi-source replication does not implement any conflict detection or resolution when applying the transactions, and those tasks are left to the application if required.
In a multi-source replication topology, a slave creates a replication channel for each master that it should receive transactions from. For more information, see Section 5.3, “Replication Channels”. The error codes and messages that are issued when multi-source replication is enabled specify the channel that generated the error.
This section provides tutorials on how to configure masters and slaves for multi-source replication, how to start, stop and reset multi-source slaves, and how to monitor multi-source replication.