Sometimes you want to clear all replication information from the library, such as switching to a different master, master-slave redo, and so on; the reset slave is a dangerous command, so be sure to be prepared to know what it means before you execute it.
1. The command is executed on the slave and must be stopped before execution slave (stop slave)
2. After you perform reset slave, all information related to replication is cleared, including: Master.info, relay-log.info, and unconditional removal of all relay logs (relay logs). Note that it is unconditional, that is, not managing your slave SQL thread to replay all relay logs.
3. Note that after the stop slave, save the show slave status information before performing the reset slave. This information will be useful in general.
Www.it165.net
Online used once, due to the master-slave inconsistency, and xtrabackup to restore the data, at that time, understanding is not too clear, and urgent, so on the implementation, redo; At that time, the heart still has no end.
Also explained that: do not use the master-slave data Catalog to compare the master-slave, this is a completely stupid way, that is, when executed, a look at the directory of the main cubby from the library dozens of M, at that time on the heartbeat, check the specific data, are the same, do not scare themselves, hehe.
So before executing the command, you must fully understand what happens when this command goes down, and whether it affects production applications.