Syntax:
RESET MASTER

*Warning*:

Use this statement with caution to ensure you do not lose any wanted
binary log file data and GTID execution history.

RESET MASTER requires the RELOAD privilege.

For a server where binary logging is enabled (log_bin is ON), RESET
MASTER deletes all existing binary log files and resets the binary log
index file, resetting the server to its state before binary logging was
started. A new empty binary log file is created so that binary logging
can be restarted.

For a server where GTIDs are in use (gtid_mode is ON), issuing RESET
MASTER resets the GTID execution history. The value of the gtid_purged
system variable is set to an empty string (''), the global value (but
not the session value) of the gtid_executed system variable is set to
an empty string, and the mysql.gtid_executed table is cleared (see
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html
#replication-gtids-gtid-executed-table). If the GTID-enabled server has
binary logging enabled, RESET MASTER also resets the binary log as
described above. Note that RESET MASTER is the method to reset the GTID
execution history even if the GTID-enabled server is a replica where
binary logging is disabled; RESET SLAVE has no effect on the GTID
execution history. For more information on resetting the GTID execution
history, see
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-lifecycle.html
#replication-gtids-execution-history.

URL: https://dev.mysql.com/doc/refman/5.7/en/reset-master.html

