Updates, Order, & the Binlog
Imagine you had two separate databases, a read-write primary and a read-only replica, and you wanted to keep a table between them synchronized. Writes would occur on the primary table and should eventually appear on the replica table. To synchronize ...
nocd.hashnode.dev3 min read
Anil Vaitla
Building
For a long while MySQL only had single threaded replication, so all transactions are applied one at a time in a serial order. This meant ordering and correctness of application works (the data on the replica still matches the data on the primary), then they began to add parallel replication. This causes out of order problems (thread 1 applies before thread 2 leading to either a data mismatch or a conflict). There's some more discussion here about group commit and LOGICAL_CLOCK replication: dev.mysql.com/doc/refman/8.0/en/replication-optio…