PDF (A4) - 40.5Mb
Man Pages (TGZ) - 259.5Kb
Man Pages (Zip) - 366.7Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb
The following list shows the most common states you may see in theState column for theBinlog Dump thread of the replication source. If you see noBinlog Dump threads on a source, this means that replication is not running; that is, that no replicas are currently connected.
Set theterminology_use_previous system variable with session scope to support individual functions, or global scope to be a default for all new sessions. When global scope is used, the slow query log contains the old versions of the names.
Finished reading one binlog; switching to next binlogThe thread has finished reading a binary log file and is opening the next one to send to the replica.
Master has sent all binlog to slave; waiting for more updatesSource has sent all binlog to replica; waiting for more updatesThe thread has read all remaining updates from the binary logs and sent them to the replica. The thread is now idle, waiting for new events to appear in the binary log resulting from new updates occurring on the source.
Sending binlog event to replicaBinary logs consist ofevents, 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 replica.
Waiting to finalize terminationA very brief state that occurs as the thread is stopping.
PDF (A4) - 40.5Mb
Man Pages (TGZ) - 259.5Kb
Man Pages (Zip) - 366.7Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb