Skip to main content

Slave has read all relay log; waiting for the slave i-o thread to update it

Short Description

All relay log events have been processed, 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​

MariaDB Source → Replica replication is in use. The relay log is sited in the slave and records the transactions sent from the master. 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.

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.