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.8 LOAD DATA FROM MASTER (slave)
Takes a snapshot of the master and copies
it to the slave.
Updates the values of MASTER_LOG_FILE and
MASTER_LOG_POS so that the slave will start replicating from the
correct position. Will honor table and database exclusion rules
specified with replicate-* options. So far works only with
MyISAM tables and acquires a global read lock on the master while
taking the snapshot. In the future it is planned to make it work with
InnoDB tables and to remove the need for global read lock using
the non-blocking online backup feature.
If you are loading big tables, you may have to increase the values
of net_read_timeout and net_write_timeout
on both your master and slave ; see section 4.5.7.4 SHOW VARIABLES.
Note that LOAD DATA FROM MASTER does NOT copy any
tables from the mysql database. This is to make it easy to have
different users and privileges on the master and the slave.
Requires that the replication user which is used to connect to the master has
RELOAD and SUPER privileges on the master,
SELECT privileges on all master's tables you want to load. All
master's tables on which the user has no SELECT privilege will
be ignored by LOAD DATA FROM MASTER; this is because the
master will hide them to the user: LOAD DATA FROM MASTER calls
SHOW DATABASES to know the master databases to load, but
SHOW DATABASES returns only databases on which the user has
some privilege, see section 4.5.7.1 Retrieving information about Database, Tables, Columns, and Indexes.
On the slave's side, the user which issues LOAD DATA FROM MASTER should
have grants to drop and create the involved databases and tables.
