MySQL Manual
4 Database Administration
- 4.10 Replication in MySQL
- 4.10.7 SQL Commands Related to Replication
- 4.10.7.1
START SLAVE(slave) - 4.10.7.2
STOP SLAVE(slave) - 4.10.7.3
SET SQL_LOG_BIN=0|1(master) - 4.10.7.4
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=n(slave) - 4.10.7.5
RESET MASTER(master) - 4.10.7.6
RESET SLAVE(slave) - 4.10.7.7
LOAD TABLE tblname FROM MASTER(slave) - 4.10.7.8
LOAD DATA FROM MASTER(slave) - 4.10.7.9
CHANGE MASTER TO master_def_list(slave) - 4.10.7.10
MASTER_POS_WAIT()(slave) - 4.10.7.11
SHOW MASTER STATUS(master) - 4.10.7.12
SHOW SLAVE HOSTS(master) - 4.10.7.13
SHOW SLAVE STATUS(slave) - 4.10.7.14
SHOW MASTER LOGS(master) - 4.10.7.15
SHOW BINLOG EVENTS(master) - 4.10.7.16
PURGE MASTER LOGS(master)
- 4.10.7.1
4.10.7.1 START SLAVE (slave)
Starts the slave threads. Was called SLAVE START in MySQL 3.23.
As of MySQL 4.0.2, you can add IO_THREAD or SQL_THREAD
options to the statement to start only the I/O thread or the SQL thread.
The I/O thread reads queries from the master server and stores them in the
relay log. The SQL thread reads the relay log and executes the
queries.
Note that if START SLAVE succeeds in starting the slave threads it
will return without any error. But even in that case it might be that slave
threads start and then later stop (because they don't manage to
connect to the master or read his binlogs or any other
problem). START SLAVE will not warn you about this, you have to
check your slave's `.err' file for error messages generated by
the slave threads, or check that these are running fine with SHOW
SLAVE STATUS.
