Syntax:
STOP SLAVE [thread_types]

thread_types:
    [thread_type [, thread_type] ... ]

thread_type: IO_THREAD | SQL_THREAD

Stops the slave threads. STOP SLAVE requires the SUPER privilege.
Recommended best practice is to execute STOP SLAVE on the slave before
stopping the slave server (see
http://dev.mysql.com/doc/refman/5.6/en/server-shutdown.html, for more
information).

When using the row-based logging format: You should execute STOP SLAVE
or STOP SLAVE SQL_THREAD 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).

Like START SLAVE, this statement may be used with the IO_THREAD and
SQL_THREAD options to name the thread or threads to be stopped.

In MySQL 5.6.7 and later, STOP SLAVE causes an implicit commit of an
ongoing transaction. See
http://dev.mysql.com/doc/refman/5.6/en/implicit-commit.html.

Beginning with MySQL 5.6.11, gtid_next must be set to AUTOMATIC before
issuing this statement (Bug #16062608).

In MySQL 5.6.13 and later, you can control how long STOP SLAVE waits
before timing out by setting the rpl_stop_slave_timeout system
variable. This can be used to avoid deadlocks between STOP SLAVE and
other slave SQL statements using different client connections to the
slave. (Bug #16856735)

*Note*: In MySQL 5.6, STOP SLAVE waits until the 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 KILL CONNECTION statement. (Bug #319, Bug
#38205)

URL: http://dev.mysql.com/doc/refman/5.6/en/stop-slave.html

