Another reason why SQL_SLAVE_SKIP_COUNTER is bad in MySQL

(Jervin Real) It is everywhere in the world of MySQL that if your replication is broken because an event caused a duplicate key or a row was not found and it cannot be updated or deleted, then you can use ‘ STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE; ’ and be done with it. In some

Read More - Register for Free Membership