Oracle 5.0 Reference Manual page 1148

case, the old values for the master binary log file name and position are considered no longer
applicable, so if you do not specify
MASTER_LOG_FILE=''
Setting MASTER_HOST=''—that is, setting its value explicitly to an empty string—is not the same as
not setting it at all. Setting this option to an empty string causes
(Bug #28796)
• and
MASTER_USER MASTER_PASSWORD
connecting to the master.
Currently, a password used for a replication slave account is effectively limited to 32 characters in
length; the password can be longer, but any excess characters are truncated. This is not due to any
limit imposed by the MySQL Server generally, but rather is an issue specific to MySQL Replication.
(For more information, see Bug #43439.)
The text of a running
MASTER_PASSWORD, can be seen in the output of a concurrent
The
MASTER_SSL_xxx
correspond to the
--ssl-xxx
Section 16.3.7, "Setting Up Replication Using
that are compiled without SSL support. They are saved to the
slave does not have SSL support enabled.
MASTER_CONNECT_RETRY
is 60. The number of reconnection attempts is limited by the
server option; for more information, see
Variables".
and
MASTER_LOG_FILE
should begin reading from the master the next time the thread starts.
are the coordinates at which the slave SQL thread should begin reading
RELAY_LOG_POS
from the relay log the next time the thread starts. If you specify either of
or MASTER_LOG_POS, you cannot specify
or
MASTER_LOG_FILE
SQL thread before
CHANGE MASTER TO
replication, even if the slave SQL thread was late compared to the slave I/O thread, when you merely
want to change, say, the password to use.
deletes all relay log files and starts a new one, unless you specify
CHANGE MASTER TO
or RELAY_LOG_POS. In that case, relay log files are kept; the
RELAY_LOG_FILE
[489]
relay_log_purge
is useful for setting up a slave when you have the snapshot of the master and
CHANGE MASTER TO
have recorded the master binary log coordinates corresponding to the time of the snapshot. After
loading the snapshot into the slave to synchronize it to the slave, you can run
TO MASTER_LOG_FILE='log_name', MASTER_LOG_POS=log_pos
coordinates at which the slave should begin reading the master binary log.
The following example changes the master server the slave uses and establishes the master binary
log coordinates from which the slave begins reading. This is used when you want to set up the slave to
replicate the master:
CHANGE MASTER TO
MASTER_HOST='master2.mycompany.com',
MASTER_USER='replication',
MASTER_PASSWORD='bigs3cret',
MASTER_PORT=3306,
MASTER_LOG_FILE='master2-bin.001',
MASTER_LOG_POS=4,
MASTER_CONNECT_RETRY=10;
SQL Statements for Controlling Slave Servers
MASTER_LOG_FILE
and
MASTER_LOG_POS=4
are the user name and password of the account to use for
CHANGE MASTER TO
options provide information about using SSL for the connection. They
options described in
specifies how many seconds to wait between connect retries. The default
Section 16.1.2, "Replication and Binary Logging Options and
are the coordinates at which the slave I/O thread
MASTER_LOG_POS
RELAY_LOG_FILE
is specified, the slave uses the last coordinates of the slave
MASTER_LOG_POS
was issued. This ensures that there is no discontinuity in
global variable is set silently to 0.
1128
and
MASTER_LOG_POS
are silently appended to it.
START SLAVE
statement, including values for
SHOW PROCESSLIST
Section 6.3.6.4, "SSL Command
SSL". These options can be changed even on slaves
master.info
--master-retry-count
or RELAY_LOG_POS. If neither of
in the statement,
subsequently to fail.
MASTER_USER
statement.
Options", and
file, but are ignored if the
[1454]
and
RELAY_LOG_FILE
MASTER_LOG_FILE
CHANGE MASTER
on the slave to specify the
and