Table missing records... but replication says OK.

[Rick Elder]

I have a replication which there sometimes is a hickup, which a demanding query needs to be killed (that is another story), which case sometimes there are missing records, even once the replication is back in "sync".

It shows 0 seconds behind master, but some tables are short records for a specific table, IE:
labdata:
Prod: 424856 Slave: 424852

The database is about 30Gb, and would take sometime to copy over the whole DB from Master to Slave. There are a number of critical tables that need to be in sync ASAP, any other tables can wait for a full DB copy.

Since replication is working, can I stop the slave copy the table files from master DB to the slave, then start replication on the slave? It should then have all the missing records, then once replication kicks on, it should have anything that has come since replication was stopped??

Thanks!