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.
Use this statement with caution to ensure you do not lose binary log file data.
RESET MASTER also clears the values of the
gtid_purged system variable as
well as the global value of the
gtid_executed system variable
(but not its session value); that is, executing this statement
sets each of these values to an empty string
''). In MySQL 5.7.5 and later, this
statement also clears the
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 by
PURGE BINARY LOGS.
RESET MASTERis not intended to be used while any replication slaves are running. The behavior of
RESET MASTERwhen used while slaves are running is undefined (and thus unsupported), whereas
PURGE 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 16.1.2, “Setting Up Binary Log File Position Based Replication”).
Execute a few test queries on the master.
Check that the queries were replicated to the slave.
RESET MASTERon the master to clean up the test queries.
After verifying the setup, resetting the master and slave and ensuring that no unwanted data or binary log files generated by testing remain on master or slave, you can start the slave and begin replicating.