MySQL GTID replication
Traditional MySQL replication is based on relative coordinates — each
replica keeps track of its position with respect to its current
master's binary log files.
GTID enhances this setup by assigning a unique identifier to every
transaction, and each MySQL server keeps track of which transactions
it has already executed.
This permits "auto-positioning," the ability for a replica to be
pointed at a master instance without needing to specify a binlog
filename or position in the CHANGE MASTER statement.
replica keeps track of its position with respect to its current
master's binary log files.
GTID enhances this setup by assigning a unique identifier to every
transaction, and each MySQL server keeps track of which transactions
it has already executed.
This permits "auto-positioning," the ability for a replica to be
pointed at a master instance without needing to specify a binlog
filename or position in the CHANGE MASTER statement.
Comments
Post a Comment