Rechercher dans le manuel MySQL
8.14.4 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.
A state that occurs very briefly, after the connection to the master is established.
The thread is attempting to connect to the master.
Queueing master event to the relay log
The thread has read an event and is copying it to the relay log so that the SQL thread can process it.
Reconnecting after a failed binlog dump request
The thread is trying to reconnect to the master.
Reconnecting after a failed master event read
The thread is trying to reconnect to the master. When connection is established again, the state becomes
Waiting for master to send event
.A state that occurs very briefly after the connection to the master is established.
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 for its turn to commit
A state that occurs when the slave thread is waiting for older worker threads to commit if
slave_preserve_commit_order
is enabled.Waiting for master to send event
The thread has connected to the master and is waiting for binary log events to arrive. This can last for a long time if the master is idle. If the wait lasts for
slave_net_timeout
seconds, a timeout occurs. At that point, the thread considers the connection to be broken and makes an attempt to reconnect.The initial state before
Connecting to master
.Waiting for slave mutex on exit
A state that occurs briefly as the thread is stopping.
Waiting for the slave SQL thread to free enough relay log space
You are using a nonzero
relay_log_space_limit
value, and the relay logs have grown large enough that their combined size exceeds this value. The I/O thread is waiting until the SQL thread frees enough space by processing relay log contents so that it can delete some relay log files.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.Waiting to reconnect after a failed master event read
An error occurred while reading (due to disconnection). The thread is sleeping for the number of seconds set by the
CHANGE MASTER TO
statement (default 60) before attempting to reconnect.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-slave-io-thread-states.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.