Asynchronous replication
When we configure a server as a slave, the replication is initiated by the slave process itself, by communicating with the master server. The slave process will ask the active server to provide updates since the last update it received. The master process will be responsible to logging the events on every state change. It doesn't stop executing transactions if the slave is lagging behind or even if the slave is not reachable. Thus, this type of replication is called asynchronous replication.
In earlier releases of MySQL asynchronous replication, you could not deny the loss of transactional data on slaves, even if you were using the InnoDB engine and setting sync_binlog to 1. For example, we use the InnoDB engine and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access