Using MySQL Global Transaction IDs in Production
- Track: MySQL and friends devroom
- Room: UA2.114 (Baudoux)
- Day: Sunday
- Start: 10:05
- End: 10:25
MySQL 5.6 introduced Global Transaction IDs to make the reconfiguration of replication straightforward. The key benefit is that you can instantly and reliably change your replication topology if a node goes down or if the current topology no longer fits your needs. But of course operating a GTID-based cluster brings new challenges: old habits no longer work, tools have changed, and new issues have appeared.
MySQL 5.6 introduced Global Transaction IDs to make the reconfiguration of replication straightforward. The key benefit is that you can instantly and reliably change your replication topology if a node goes down or if the current topology no longer fits your needs. But of course operating a GTID-based cluster brings new challenges: old habits no longer work, tools have changed, and new issues have appeared.
In this session, you will learn about using GTIDs in production, including: - How to execute the daily DBA tasks related to GTID-based replication, such as monitoring replication status or recovering from replication errors - The new options for high availability and the tools that can help you - What can go wrong when using GTIDs
Speakers
 |
Stephane Combaudon |