In this section, we discuss transaction-based replication using global transaction identifiers (GTIDs). When using GTIDs, each transaction can be identified and tracked as it is committed on the originating server and applied by any slaves; this means that it is not necessary when using GTIDs to refer to log files or positions within those files when starting a new slave or failing over to a new master, which greatly simplifies these tasks. Because GTID-based replication is completely transaction-based, it is simple to determine whether masters and slaves are consistent; as long as all transactions committed on a master are also committed on a slave, consistency between the two is guaranteed. You can use either statement-based or row-based replication with GTIDs (see Section 16.1.2, “Replication Formats”); however, for best results, we recommend that you use the row-based format.
The next few sections discuss the following topics:
How GTIDs are defined and created, and how they are represented in the MySQL Server (see Section 188.8.131.52, “GTID Concepts”).
A general procedure for setting up and starting GTID-based replication (see Section 184.108.40.206, “Setting Up Replication Using GTIDs”).
Suggested methods for provisioning new replication servers when using GTIDs (see Section 220.127.116.11, “Using GTIDs for Failover and Scaleout”).
Restrictions and limitations that you should be aware of when using GTID-based replication (see Section 18.104.22.168, “Restrictions on Replication with GTIDs”).
For information about MySQL Server options and variables relating to GTID-based replication, see Section 22.214.171.124, “Global Transaction ID Options and Variables”. See also Section 12.15, “Functions Used with Global Transaction IDs”, which describes SQL functions supported by MySQL 5.7 for use with GTIDs.