STOP SLAVE [
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.11, “The Server Shutdown Process”, for more information).
When using the row-based logging format:
Prior to MySQL 5.1.35, you should always
STOP SLAVE on the slave before
stopping the slave server to help avoid the possibility of an
inconsistent slave; in MySQL 5.1.35 and later, you should
execute this statement 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.1.55 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.
The transactional behavior of
SLAVE changed in MySQL 5.1.35. Previously, it took
effect immediately. Beginning with MySQL 5.1.35, it waits
until any current replication event group affecting one or
more nontransactional tables has finished executing (if there
is any such replication group), or until the user issues a
KILL QUERY or
CONNECTION statement. (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.1 for backward compatibility,
but is deprecated and is removed in MySQL 5.6.