This article provides a comprehensive, hands‑on guide to MySQL master‑slave replication, covering the underlying architecture, binlog formats, GTID and semi‑synchronous modes, detailed configuration steps, thread workflows, common failure scenarios with step‑by‑step diagnostics, and practical monitoring and failover scripts.
This article explains why MySQL master‑slave replication lag causes dirty reads, breaks down the asynchronous replication pipeline, and presents three practical mitigation strategies—including semi‑synchronous replication, forcing reads from the master, and cache double‑delete techniques—so you can choose the right solution for your workload.
This article explains why MySQL master‑slave replication can become delayed—including single‑threaded binlog processing, high load, network latency, and configuration issues—and provides detailed troubleshooting steps and practical solutions such as semi‑synchronous replication, hardware upgrades, and configuration tuning.
This article explains MySQL master‑slave replication, covering its three modes (asynchronous, semi‑synchronous, and fully synchronous), the underlying binary‑log mechanism, key replication threads, configuration steps, and includes a promotional notice for an upcoming live career‑development session.
An in‑depth guide explains MySQL replication fundamentals, compares asynchronous, semi‑synchronous, and fully synchronous modes, and details the binlog‑based architecture with its I/O, log dump, and SQL threads, helping readers understand how replication improves scalability and data safety.
MySQL replication copies data changes from a primary server to one or more replicas using binlog events—supporting statement, row, or mixed formats and GTID positioning—to provide real‑time backup, read‑write separation, high‑availability failover, and integration pipelines via asynchronous, semi‑synchronous, or centralized binlog services.
This article explains MySQL master‑slave replication, covering replication modes, use cases, required configurations, underlying mechanisms, common issues, and solutions such as semi‑synchronous and parallel replication, along with practical configuration examples and monitoring commands.
This article compares MySQL semi‑synchronous and asynchronous replication, presenting performance test results that show only a small difference in TPS and QPS, explains why the gap is minimal, and provides step‑by‑step instructions and sysbench scripts for setting up and benchmarking both replication modes.
This article details UDB's high‑availability architecture and four kernel‑level optimizations—binlog replication, relay‑log recording, master.info handling, and relay‑log locking—that together improve MySQL semi‑synchronous replication performance and reliability.
