This article details a systematic approach to diagnose and resolve MySQL 8.0 replication lag by enabling WRITESET on the source, configuring LOGICAL_CLOCK with optimal worker count on the replica, and preserving commit order, complete with diagnostic queries, configuration steps, and validation metrics.
When MySQL replication latency jumps from milliseconds to 10 seconds, blindly raising replica_parallel_workers won’t help; the article walks through diagnosing the delay, then applies three concrete parallel‑replication optimizations—enabling WRITESET on the source, configuring LOGICAL_CLOCK with appropriate applier workers, and optionally preserving commit order—while showing the required SQL commands, monitoring queries, and rollback steps.
The article investigates why master‑slave replication delay spikes each morning between 05:00 and 07:00, tracing it to the inventory‑snapshot worker that floods binlog traffic, evaluates five mitigation strategies, implements a big‑data extraction pipeline to Elasticsearch, and reports that the nightly delay disappeared and disk utilization improved.
This article explains why master‑slave lag occurs in MySQL, describes the evolution of parallel replication schemes—including group‑commit, Commit‑Parent‑Based, Lock‑Based, and WRITESET approaches—shows benchmark results, and provides practical configuration steps to enable high‑performance parallel replication.
This article explains why MySQL slave lag is a critical issue, compares the official parallel replication schemes—including Commit‑Parent‑Based, Lock‑Based, and WRITESET—details their internal mechanisms, presents benchmark results, and provides the exact configuration parameters needed to enable high‑performance parallel replication.
This article explains how MySQL’s logical‑clock replication can be enhanced with writeset‑based dependency tracking, detailing the underlying theory, code implementation, configuration options, performance testing, and practical considerations for improving parallel applier concurrency.
This article explains MySQL's write‑set based parallel replication, detailing how writeset hashes are generated, stored in a historical map, and used to adjust the last‑commit value for improved parallel replay, including configuration parameters, code examples, and the impact of different dependency‑tracking modes.
This article explains the evolution of MySQL replication, from the classic master‑slave model to schema‑level and group‑commit parallelism in 5.7, and finally the WriteSet‑based parallel replication introduced in MySQL 8.0, including configuration parameters, conflict‑detection logic, and performance test results.
