Errant transactions are a major issue when using GTID replication. Although this isn’t something new, the drawbacks are more notorious with GTID than with regular replication.
The situation where errant transaction bites you is a common DBA
task: Failover. Now that tools like MHA have
support for GTID replication (starting from 0.56
version), this protocol is becoming more popular, and so
are the issues with errant transactions. Luckily, the fix is
as simple as …