Replication Slave I/O Thread States
741
The following list shows the most common states you may see in the
State
column for the master's
Binlog Dump
thread. If you see no
Binlog Dump
threads on a master server, this means that
replication is not running—that is, that no slaves are currently connected.
•
Sending binlog event to slave
Binary logs consist of events, where an event is usually an update plus some other information. The
thread has read an event from the binary log and is now sending it to the slave.
•
Finished reading one binlog; switching to next binlog
The thread has finished reading a binary log file and is opening the next one to send to the slave.
•
Has sent all binlog to slave; waiting for binlog to be updated
The thread has read all outstanding updates from the binary logs and sent them to the slave. The
thread is now idle, waiting for new events to appear in the binary log resulting from new updates
occurring on the master.
•
Waiting to finalize termination
A very brief state that occurs as the thread is stopping.
8.10.6. Replication Slave I/O Thread States
The following list shows the most common states you see in the
State
column for a slave server I/O
thread. This state also appears in the
Slave_IO_State
column displayed by
SHOW SLAVE STATUS
,
so you can get a good view of what is happening by using that statement.
•
Waiting for master update
The initial state before
Connecting to master
.
•
Connecting to master
The thread is attempting to connect to the master.
•
Checking master version
A state that occurs very briefly, after the connection to the master is established.
•
Registering slave on master
A state that occurs very briefly after the connection to the master is established.
•
Requesting binlog dump
A state that occurs very briefly, after the connection to the master is established. The thread sends
to the master a request for the contents of its binary logs, starting from the requested binary log file
name and position.
•
Waiting to reconnect after a failed binlog dump request
If the binary log dump request failed (due to disconnection), the thread goes into this state while it
sleeps, then tries to reconnect periodically. The interval between retries can be specified using the
CHANGE MASTER TO
statement or the
--master-connect-retry
[1453]
option.
•
Reconnecting after a failed binlog dump request
The thread is trying to reconnect to the master.
•
Waiting for master to send event
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 ...