STOP SLAVE [thread_types] thread_types: [thread_type [, thread_type] ... ] thread_type: IO_THREAD | SQL_THREAD
Stops the slave threads.
SLAVE requires the
SUPER privilege. Recommended
best practice is to execute
STOP SLAVE on the
slave before stopping the slave server (see
Section 5.1.13, “The Server Shutdown Process”, for more information).
When using the row-based logging format:
You should execute
STOP SLAVE on the slave
prior to shutting down the slave server if you are replicating
any tables that use a nontransactional storage engine (see the
Note later in this section). In MySQL
5.5.9 and later, you can also use
SQL_THREAD for this purpose.
START SLAVE, this statement
may be used with the
SQL_THREAD options to name the thread or
threads to be stopped.
If the current replication event group has modified one or more
nontransactional tables, STOP SLAVE waits for up to 60 seconds
for the event group to complete, unless you issue a
KILL QUERY or
statement for the slave SQL thread. If the event group remains
incomplete after the timeout, an error message is logged. (Bug
#319, Bug #38205)
In old versions of MySQL (before 4.0.5), this statement was
SLAVE STOP. This usage is still
accepted in MySQL 5.5 for backward compatibility,
but is deprecated and is removed in MySQL 5.6.