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.
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
This statement is intended to be used only when the source is started for the first time.
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 replicas are running. The behavior of
RESET MASTERwhen used while replicas are running is undefined (and thus unsupported), whereas
PURGE BINARY LOGSmay be safely used while replicas are running.
RESET MASTER can prove useful
when you first set up the source and the replica, so that you
can verify the setup as follows:
Start the source and replica, and start replication (see Section 17.1.1, “How to Set Up Replication”).
Execute a few test queries on the source.
Check that the queries were replicated to the replica.
RESET MASTERon the source 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 replica and begin replicating.