Mark Filipi (SurveyMonkey), Brian Cain (Dropbox) delivers his talk, "MySQL GTID Implementation, Maintenance, and Best Practices - The Short Version", on DAY 2 of the Percona Live Open Source Database Conference 2017, 4/26, at Santa Clara, CA.

Many MySQL shops have made the transition from MySQL 5.5 to 5.6 in the last few years, but GTID (global transaction identifier) implementation has often been considered too difficult or risky a change. MySQL 5.7 is making GTID implementation easier, but it may not yet be clear why to convert. This 50 minute presentation covers GTID concepts, the process for converting from default replication, and demonstrate techniques for being successful with GTID. It covers all the essential materials from last year's 3 hour tutorial in a condensed format.
Concepts
- Definition
- How GTIDs differ from traditional binary log positioning and advantages for converting
- GTID sets and how they relate to missing transactions, slave_parallel_workers, and slave_parallel_type
- Compare implementation steps between Oracle MySQL and Percona Server
- server_id, server_uuid, and how a new server may cause conflicts with GTID

Implementation
- Converting a running master-slave topology to use GTIDs
- Adding a new slave to create a 3-tier topology (master - relay - slave)
- Promoting a slave to master and to relay

Maintenance
- Reviewing GTID sets to determine the currently writing master
- Demonstrating GTID set gaps caused by parallelism versus missing transactions
- Finding extra or missing transactions within the binary log
- Correcting missing data using gtid_next and “faking” a transaction to correct out of sync issues

New 5.7 Features and Advanced Concepts
- Replication feature changes in 5.7
- Specific settings to tune or ignore for 5.6 and 5.7


Stored Under: Percona Live Sessions, MySQL, Percona Server