During the last few weeks, I\u2019ve spent quite a bit of time working on different proofs of concept for our MySQL servers. During my tests, I broke MySQL\u2019s replication more than once. I always had to turn to Google to get the specific query to run to fix it, when I only wanted to skip one event.<\/p>\n
So since it\u2019s easier for me, I\u2019ll keep it here on my blog. Hopefully, that can help someone else too.<\/p>\n
So. You happen to check the status of your slave and it\u2019s not replicating anymore. As you can see below, the Seconds_Behind_Master is NULL. That\u2019s not good. You can also see the ID of the last error. You can verify with SHOW SLAVE STATUS that your slave is now functioning properly.<\/p>\n","protected":false},"excerpt":{"rendered":" During the last few weeks, I\u2019ve spent quite a bit of time working on different proofs of concept for our<\/p>\n
\n<\/a>
\nIn order to get the slave to skip that transaction, you need to follow this procedure:<\/p>\nmysql>STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;<\/pre>\n