Repair MySQL 5.6 GTID replication by injecting empty transactions

Since Sql_slave_skip_counter doesn ' t work with GTID we-need to find a-to-ignore that transaction. The It is creating a new empty transaction with it the GTID we want to skip.

STOP SLAVE; SET Gtid_next="7d72f9b4-8577-11e2-a3d7-080027635ef5:5"; BEGIN; COMMIT; SET Gtid_next="AUTOMATIC"; START SLAVE; [.. . ]retrieved_gtid_set : 7d72f9b4-8577-11e2- a3d7-080027635ef5 : 1-5 executed_gtid_set: 7d72f9b4-8577-11e2-a3d7-080027635ef5: 1-5   

After the START SLAVE the SLAVE checks that transaction 5 are already in their own binary log and that means then it has been Executed.

This is a easy and easy-to-skip some transactions but take-in account, the by doing, this you'll end up with data inconsisten Cies between Master and Slave servers. Pt-table-checksum can help you here, which are found in Percona Toolkit for MySQL.

Last week I gave a on Percona MySQL University @Toronto about GTID. It includes an overview of MySQL 5.6 GTID, can help people to start working with this new feature in MySQL 5.6. Here is the slides from this session. I hope you find it useful:mysql 5.6 GTID in a nutshell

Repair MySQL 5.6 GTID replication by injecting empty transactions