Available since 10.0.0
- Multi-source replication (MDEV-253)
- Multi-source replication is a longtime wish of many users. In scenarios where you partition your data over many masters you can then replicate the data from all masters onto one slave. Typical use cases are:
- Data partitioned over many masters can be pulled together onto one slave for analytical queries
- Many masters can replicate to the same slave and a complete backup can be done on the slave
- Newer hardware usually provides more performance. Usually all hardware isn’t upgraded at once and multi-source can be used for replicating many masters to a powerful new slave.
- Original code from Taobao
- Multi-source replication is a longtime wish of many users. In scenarios where you partition your data over many masters you can then replicate the data from all masters onto one slave. Typical use cases are:
Более подробное описание
https://mariadb.atlassian.net/browse/MDEV-253
Each master is handled by a specific replicator instance in the slave server. Each replicator instance consists of separate I/O thread, SQL thread, and associated state and configuration. In efffect, several replication slaves are running at the same time, each replicating from a separate master, but all replicating into a common data store (typically, but not necessarily to separate databases/tables).
A replicator instance is identified with a user-chosen name used in replication SQL statements such as CHANGE MASTER TO ... This name is also included in file names to distinguish the files that keep the replication state (relay logs, master.info, relay-log.info). This way, each separate instance can be configured separately, but otherwise the same way as existing single-source replication.
синтаксис
https://mariadb.com/kb/en/multi-source-replication/
Комментариев нет:
Отправить комментарий