SQL Statements for Controlling Slave Servers
1131
Option
Maximum Length
MASTER_LOG_FILE
255
RELAY_LOG_FILE
255
MASTER_SSL_CA
255
MASTER_SSL_CAPATH
255
MASTER_SSL_CERT
255
MASTER_SSL_KEY
255
MASTER_SSL_CIPHER
511
13.4.2.5.
RESET SLAVE
Syntax
RESET SLAVE
RESET SLAVE
makes the slave forget its replication position in the master's binary log. This statement
is meant to be used for a clean start: It deletes the
master.info
and
relay-log.info
files, all the
relay log files, and starts a new relay log file. To use
RESET SLAVE
, the slave replication threads must
be stopped (use
STOP SLAVE
if necessary).
Note
All relay log files are deleted, even if they have not been completely executed
by the slave SQL thread. (This is a condition likely to exist on a replication slave
if you have issued a
STOP SLAVE
statement or if the slave is highly loaded.)
Connection information stored in the
master.info
file is immediately reset using any values specified
in the corresponding startup options. This information includes values such as master host, master
port, master user, and master password. Options for which values are not specified are cleared. If the
slave SQL thread was in the middle of replicating temporary tables when it was stopped, and
RESET
SLAVE
is issued, these replicated temporary tables are deleted on the slave.
13.4.2.6.
SET GLOBAL sql_slave_skip_counter
Syntax
SET GLOBAL sql_slave_skip_counter =
N
This statement skips the next
N
events from the master. This is useful for recovering from replication
stops caused by a statement.
This statement is valid only when the slave threads are not running. Otherwise, it produces an error.
When using this statement, it is important to understand that the binary log is actually organized as a
sequence of groups known as event groups. Each event group consists of a sequence of events.
• For transactional tables, an event group corresponds to a transaction.
• For nontransactional tables, an event group corresponds to a single SQL statement.
Note
A single transaction can contain changes to both transactional and
nontransactional tables.
When you use
SET GLOBAL sql_slave_skip_counter
to skip events and the result is in the
middle of a group, the slave continues to skip events until it reaches the end of the group. Execution
then starts with the next event group.
13.4.2.7.
START SLAVE
Syntax
START SLAVE [
thread_types
]
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...