RESET SLAVE
RESET SLAVE makes the slave
forget its replication position in the master's binary log. This
statement is meant to be used for a clean start: It deletes the
master.info and
relay-log.info files, all the relay log
files, and starts a new relay log file. To use
RESET SLAVE, the slave
replication threads must be stopped (use
STOP SLAVE if necessary).
All relay log files are deleted, even if they have not been
completely executed by the slave SQL thread. (This is a
condition likely to exist on a replication slave if you have
issued a STOP SLAVE statement
or if the slave is highly loaded.)
In MySQL 5.5 (unlike the case in MySQL 5.1 and
earlier), RESET SLAVE does not
change any replication connection parameters such as master
host, master port, master user, or master password. (This means
that START SLAVE can be issued
without requiring a CHANGE MASTER
TO statement following RESET
SLAVE.) However, connection parameters (which are now
retained in memory even after RESET
SLAVE is issued) are reset if the slave is shut down.
If the slave SQL thread was in the middle of replicating
temporary tables when it was stopped, and
RESET SLAVE is issued, these
replicated temporary tables are deleted on the slave.