Oracle 5.0 Reference Manual page 1497

server to purge its binary logs sooner because it no longer needs to wait for the slave to fetch their
contents.
The
SHOW PROCESSLIST
master and on the slave regarding replication. For information on master states, see
"Replication Master Thread
States", and Section 8.10.7, "Replication Slave SQL Thread
The following example illustrates how the three threads show up in the output from
PROCESSLIST.
On the master server, the output from
mysql> SHOW PROCESSLIST\G
*************************** 1. row ***************************
Id: 2
User: root
Host: localhost:32931
db: NULL
Command: Binlog Dump
Time: 94
State: Has sent all binlog to slave; waiting for binlog to
be updated
Info: NULL
Here, thread 2 is a
Binlog Dump
information indicates that all outstanding updates have been sent to the slave and that the master is
waiting for more updates to occur. If you see no
that replication is not running; that is, no slaves are currently connected.
On a slave server, the output from
mysql> SHOW PROCESSLIST\G
*************************** 1. row ***************************
Id: 10
User: system user
Host:
db: NULL
Command: Connect
Time: 11
State: Waiting for master to send event
Info: NULL
*************************** 2. row ***************************
Id: 11
User: system user
Host:
db: NULL
Command: Connect
Time: 11
State: Has read all relay log; waiting for the slave I/O
thread to update it
Info: NULL
The information indicates that thread 10 is the I/O thread that is communicating with the master
State
server, and thread 11 is the SQL thread that is processing the updates stored in the relay logs. At the
time that
SHOW PROCESSLIST
The value in the column can show how late the slave is compared to the master. See
Time
Section B.13, "MySQL 5.0 FAQ:
activity on the
Binlog Dump
for any other client connection, the timeouts for this depend on the values of
and net_retry_count; for more information about these, see
Variables".
The
SHOW SLAVE STATUS
slave server. See Section 16.1.3.1, "Checking Replication
Replication Implementation Details
statement provides information that tells you what is happening on the
States". For slave states, see
SHOW PROCESSLIST
replication thread that services a connected slave. The
Binlog Dump
SHOW PROCESSLIST
was run, both threads were idle, waiting for further updates.
Replication". If sufficient time elapses on the master side without
thread, the master determines that the slave is no longer connected. As
statement provides additional information about replication processing on a
1477
Section 8.10.6, "Replication Slave I/O Thread
States".
looks like this:
threads on a master server, this means
looks like this:
net_write_timeout
Section 5.1.4, "Server System
Status".
Section 8.10.5,
SHOW
State