Slave has read all relay log; waiting for more updates
The thread has processed all events in the relay log files, and is now waiting for the I/O thread to write new events to the relay log.
Disclaimer​
The terms master and slave have historically been used by vendors in database wait events. DBmarlin does not support or condone the use of these terms. As vendors remove these terms from their software, occurrences will reduce.
Detailed Description​
Source → Replica replication is in use. The relay log is sited in the replica and records the transactions sent from the source. This wait state occurs when the replica has read all the relay log records and is waiting for new records to be sent from the source.
How to reduce this wait​
This idle wait state will normally be seen in databases with Source → Replica replication running.
Additional Links​
- MySQL Documentation - Replication Thread States - Slave has read all relay log; waiting for more updates
- MySQL Documentation - General thread states - Executing
- MySQL docs - Replication Administration Status
- INFOHUBBLOG - MySQL Master Slave Replication | Complete Guide
Search online​
If this article doesn't have the information you need you can try searching online. Remember, you can contribute suggestions to this page.