Related Documentation Download this Excerpt
PDF (US Ltr) - 1.2Mb
PDF (A4) - 1.2Mb
HTML Download (TGZ) - 329.3Kb
HTML Download (Zip) - 344.1Kb

MySQL Replication  /  Replication Configuration  /  Replication with Global Transaction Identifiers

2.3 Replication with Global Transaction Identifiers

This section explains transaction-based replication using global transaction identifiers (GTIDs), introduced in MySQL 5.6.5. 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 2.2, “Replication Formats”); however, for best results, we recommend that you use the row-based format.

This section discusses the following topics:

For information about MySQL Server options and variables relating to GTID-based replication, see Section 2.4.5, “Global Transaction ID Options and Variables”. See also Functions Used with Global Transaction IDs, which describes SQL functions supported by MySQL 5.6 for use with GTIDs.


GTIDs are not compatible or supported with the NDB storage engine used by NDB Cluster. Enabling GTIDs in NDB Cluster is very likely to cause problems with NDB, and to cause NDB Cluster Replication to fail as well.

User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.