Step-by-step MySQL GTID Replication Setup\u00a0<\/span><\/h1>\n

---

\n

I use MySQL replication extensively, It’s simple and robust, It’s also one main reason I love MySQL lot compared to other database systems. I basically use MySQL replication for performance, scalability, high availability, reliability, failover, fault tolerance etc. I have written blogs in the past on MySQL Master-Slave (\u00a0https:\/\/minervadb.com\/index.php\/2018\/01\/24\/mysql-master-slave-replication-on-ubuntu-xenial-16-04\/<\/a><\/span>\u00a0 &\u00a0https:\/\/minervadb.com\/index.php\/2018\/01\/24\/mysql-master-slave-replication-on-ubuntu-xenial-16-04-2\/<\/a><\/span>\u00a0), Master-Master replication (https:\/\/minervadb.com\/index.php\/2018\/01\/24\/mysql-master-slave-replication-on-ubuntu-xenial-16-04-2\/<\/a><\/span>) , delayed replication (https:\/\/minervadb.com\/index.php\/2018\/01\/29\/how-to-lag-a-mysql-slave-behind-to-avoid-a-data-corruption\/<\/a><\/span>) etc. \u00a0 MySQL introduced\u00a0global transaction identifiers<\/span> (GTIDs) in MySQL 5.6.5 to make failover better and easy, GTID is a global transaction identifier which consists of two entities separated by a colon (:) , GTID looks like this – {source_id:transaction_id} \/ {c03c4200-0659-11e8-94ab-0800279747b5:1-2}, \u00a0The source_id is server’s UUID<\/em> and transaction_id is a sequence number .\u00a0<\/em>I have explained below step-by-step GTID based chained replication, One master and two slaves<\/p>\n

\n
• Master<\/strong> – 192.168.56.15<\/li>\n
• Salve 1<\/strong> – 192.68.56.16<\/li>\n
• Slave 2<\/strong> – 192.168.56.17<\/li>\n<\/ul>\n
  \n

  \n

  Table of Contents<\/p>\n<\/i><\/a><\/span><\/div>\n