- Documentation Library
- Table of Contents
- MySQL 5.5 Manual
- MySQL 5.4 Manual
- MySQL 5.1 Manual
- MySQL 5.0 Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
MySQL 3.23, 4.0, 4.1 Reference Manual :: 12 SQL Statement Syntax :: 12.5 Replication Statements :: 12.5.2 SQL Statements for Controlling Slave Servers :: 12.5.2.8 STOP SLAVE Syntax
Section Navigation [Toggle]
- 12.5.2 SQL Statements for Controlling Slave Servers
- 12.5.2.1 CHANGE MASTER TO Syntax
- 12.5.2.2 LOAD DATA FROM MASTER Syntax
- 12.5.2.3 LOAD TABLE tbl_name FROM MASTER Syntax
- 12.5.2.4 MASTER_POS_WAIT() Syntax
- 12.5.2.5 RESET SLAVE Syntax
- 12.5.2.6 SET GLOBAL SQL_SLAVE_SKIP_COUNTER Syntax
- 12.5.2.7 START SLAVE Syntax
- 12.5.2.8 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, as of MySQL
4.0.2, this statement may be used with the
IO_THREAD and SQL_THREAD
options to name the thread or threads to be stopped.
This statement is called SLAVE STOP before
MySQL 4.0.5. SLAVE STOP is still accepted for
backward compatibility, but is deprecated.
User Comments
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.