Skip to main content

Master has sent all binlog to slave; waiting for binlog to be updated

Short Description

Replication source changes have been applied at a replica and more changes are being waited for.

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 place. Replication transactions are written to a binary log (binlog). All remaining transactions from the binary logs have been read and sent to the slave or replica. The replication thread is now idle, waiting for new events in the master to send to the replica.

How to reduce this wait​

This is a normal idle wait state for databases with replication set up.

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.