Using MySQL Global Transaction IDs in Production
MySQL 5.6 introduced Global Transaction IDs (GTIDs) 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 webinar, 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
About the Author
Stephane CombaudonStéphane joined Percona in July 2012, after working as a MySQL DBA for leading French companies. In real life, he lives in Paris with his wife and their twin daughters. When not in front of a computer or not spending time with his family, he likes playing chess and hiking.
How Percona Can Help You
Percona Consulting can assist with GTID configuration and help you avoid problems due to known limitations. In addition, we can provide hands-on implementation, configuration, and outsourced DBA support of GTID-enabled clusters.
Percona Support can provide support for your GTID-enabled environments, including reactive response to problems and proactive response via consultative support that covers implementation, configuration, and work-arounds for known issues.
If you'd like to discuss how Percona can help you tackle your MySQL replication challenges, please call us at 1(888) 316-9775 or 1(208) 473-2904 in the US, +44-208-133-0309 in Europe, or have us contact you.