Skip navigation links
12.6 SQL Syntax for Prepared Statements »
Section Navigation      [Toggle]

12.5.2.6. STOP SLAVE Syntax

STOP SLAVE [thread_type [, thread_type] ... ]

thread_type: IO_THREAD | SQL_THREAD

Stops the slave threads. STOP SLAVE requires the SUPER privilege.

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.

Note

In MySQL 5.5, STOP SLAVE waits until the current replication event group affecting one or more non-transactional 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)

In old versions of MySQL (before 4.0.5), this statement was called SLAVE STOP. This usage is still accepted in MySQL 5.5 for backward compatibility, but is deprecated.


User Comments

Posted by Ralf Hauser on November 25 2004 7:03pm[Delete] [Edit]

can this statement be used for a backup that allows for other (application) database operations in parallel (i.e. no locking as per http://bugs.mysql.com/bug.php?id=2264); if so, will the user apart from a slight service degradation that e.g. only 1 instead of 2 slaves are available not notice that the backup is happening (in contrast to "mysqlhotcopy ")?

or would one rather need a temporary DISCONNECT or PAUSE SLAVE command for such a backup?

see also http://dev.mysql.com/doc/mysql/en/MySQL_Cluster_Backup_Concepts.html

Add your own comment.