MySQL Replication Slave I/O Thread States
eduguru 0 Comments a timeout occurs. At that point, 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 o, after the connection to the master is established. The thread sends to the master a request for the contents of its binary logs, 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 ca, MySQL Replication Slave I/O Thread States, 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 state becomes Waiting for master to send event. Waiting for the slave SQL thread to free enough relay log space You are using a nonzero relay_log_space_limit value, the thread considers the connection to be broken and makes an attempt to reconnect. Queueing master event to the relay log The thread has read an event and is copying it to the relay log so that the S, 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 option. Reconnecting after a failed binlog dump r, 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 briefl
Waiting for master update The initial state before Connecting to master. Connecting to master The thread is attempting to connect
Read more