up vote 0 down vote favorite I have a Mysql Master Slave Replication which is working fine. Unfortunately I got some serious problems on my slave and the only chance I saw was to restart the whole replication.
Slave was stopped
I created a dump on the master with logfile and logposition informations
mysqldump --skip-lock-tables --single-transaction --flush-logs --hex-blob --master-data=2 > ~/dump.sql
I dropped the database on the Slave ( to enter the fresh data )
I inserted the fresh dump
Reset master log file and master position with information given from the dump file
Now everything worked fine for some minutes and I saw how the correct data was imported from the Master. But after 10 minutes, the slave stopped importing because there were some tables missing. After a second run, I found out, that the DROP DATABASE command, I executed on the Slave, was now executed again on the slave.
Even a RESET Slave and importing data then and proceeding from Step 3 didnt help.
How can I prevent that the commands, which have been executed on the slave since the DUMP, are not being executed again?