The following list shows the most common states you may see in
State column for the
Dump thread of the replication source. If you see no
Binlog Dump threads on a source, this means
that replication is not running; that is, that no replicas are
In MySQL 8.0.26, incompatible changes were made to
instrumentation names, including the names of thread stages,
containing the terms “master”, which is changed to
“source”, “slave”, which is changed to
“replica”, and “mts” (for
“multithreaded slave”), which is changed to
“mta” (for “multithreaded applier”).
Monitoring tools that work with these instrumentation names
might be impacted. If the incompatible changes have an impact
for you, set the
BEFORE_8_0_26 to make MySQL
Server use the old versions of the names for the objects
specified in the previous list. This enables monitoring tools
that rely on the old names to continue working until they can be
updated to use the new names.
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 thread has finished reading a binary log file and is opening the next one to send to the replica.
The 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.
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 replica.
A very brief state that occurs as the thread is stopping.