RESET MASTER
Deletes all binary log files listed in the index file, resets the binary log index file to be empty, and creates a new binary log file. This statement is intended to be used only when the master is started for the first time.
The effects of RESET MASTER
differ from those of PURGE BINARY
LOGS in 2 key ways:
RESET MASTERremoves all binary log files that are listed in the index file, leaving only a single, empty binary log file with a numeric suffix of.000001, whereas the numbering is not reset byPURGE BINARY LOGS.RESET MASTERis not intended to be used while any replication slaves are running. The behavior ofRESET MASTERwhen used while slaves are running is undefined (and thus unsupported), whereasPURGE BINARY LOGSmay be safely used while replication slaves are running.
RESET MASTER can prove useful
when you first set up the master and the slave, so that you can
verify the setup as follows:
Start the master and slave, and start replication (see Section 17.1.1, “How to Set Up Replication”).
Execute a few test queries on the master.
Check that the queries were replicated to the slave.
When replication is running correctly, issue
STOP SLAVEfollowed byRESET SLAVEon the slave, then verify that any unwanted data no longer exists on the slave.Issue
RESET MASTERon the master to clean up the test queries.
After verifying the setup and getting rid of any unwanted and log files generated by testing, you can start the slave and begin replicating.