Join Sheeri Cabral for an in-depth discussion in this video Setting up GTIDs in MySQL, part of Advanced MySQL and MariaDB.
- In MySQL, global transaction identifiers have two parts.…The first part is a source identifier,…which identifies which server the transaction came from.…This is in the form of a server UUID.…The second part of MySQL GTIDs is a transaction ID.…This is in the form of a sequence of numbers.…The first transaction ID for a server…is transaction number one.…Here is what a MySQL GTID looks like.…
If the server UUID is this string,…then a sample GTID looks like this.…This GTID is saying that this server, with this UUID,…has applied transactions one through 147…that originated from the server.…If the master changes or rights to go more than one master,…then multiple masters have originated queries.…This means that there is more than one GTID for a server.…This is called a "GTID set".…
A GTID set is a comma-separated list of one or more GTIDs,…indicating what transactions have run on the server.…Here is an example of a GTID set.…There are two servers that have written transactions,…and this server has applied…up to transaction 147 from one server,…
Want more information about MariaDB? Check out Understanding MariaDB for MySQL Users.
- Comparing MariaDB and MySQL
- Creating and using virtual columns in MariaDB
- Building Sphinx tables
- Installing HandlerSocket
- Setting up GTIDs in MariaDB and MySQL
- Audit logging in MariaDB and MySQL
- Using GIS in MariaDB and MySQL