I have a handful of rows that exist in my MySQL master but not in my slave.
Replication is running ok and these rows are unlikely to ever be referenced as it is a store-and-forget type of table. However, I want to delete these orphaned rows in order to have everything in sync and prevent any future problems.
If I issue a
DELETE statement on the master to remove the offending rows, the slave obviously won't be able to replicate it as those rows don't exist at the slave.
What are the implications of doing this?
- Will this break replication or will the slave simply ignore the problem and carry on?
- What is the recommended way to resolve this?
DELETE statement was interrupted on the master. Replication stopped as a result. I believe the same
DELETE statement was then executed on the slave before restarting replication. However, it ran to completion on the slave, resulting in more rows being deleted there.