- 188.8.131.52 Configuring Multi-Source Replication
- 184.108.40.206 Provisioning a Multi-Source Replication Slave for GTID-Based Replication
- 220.127.116.11 Adding GTID-Based Masters to a Multi-Source Replication Slave
- 18.104.22.168 Adding a Binary Log Based Master to a Multi-Source Replication Slave
- 22.214.171.124 Starting Multi-Source Replication Slaves
- 126.96.36.199 Stopping Multi-Source Replication Slaves
- 188.8.131.52 Resetting Multi-Source Replication Slaves
- 184.108.40.206 Multi-Source Replication Monitoring
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 16.2.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.