Join Sheeri Cabral for an in-depth discussion in this video Global transaction identifiers (GTIDs) and failover, part of Advanced Topics in MySQL and MariaDB.
- Traditional MySQL Replication…works by having Master Server…write statements that change data…to a log called the binary log.…Slaves read the binary log…and apply changes to their data bases.…The replication location at any point in time…is the combination of the binary log file name…and the position in the binary log file.…Each server has its own local binary log file.…One of the problems with this method of replication…is that, in order to change which server is the Master,…you have to stop the Slave, taking note of where…the Slave is in the current Master's log file and position.…
Then, you have to figure out that same point in time…in the new Master's binary log file and position.…Because each server's binary log file is local to the server,…this can be tricky to figure out.…The Global Transaction Identifier is a way…to identify a transaction globally.…This means that a transaction will have the same identifier…no matter what server you are on.…In traditional replication, a transaction is identified…by a binary log file and position,…
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