Skip to content
Tagged articles

Semi-sync Replication

10 articles · Page 1 of 1
JD Tech
JD Tech
Oct 22, 2026 · Databases

Five Layers of Database High Availability: From WAL to Orchestrator Auto-Failover

This article systematically breaks down database high availability into five layers — single-node durability via WAL and two-phase commit, master-slave replication with async and semi-sync modes, GTID-based global transaction identification, consistent failover with fencing, and automated failover using Orchestrator and probe-agent — illustrating each with real-world failure cases and configuration details.

Crash RecoveryFailoverGTID
0 likes · 25 min read
Five Layers of Database High Availability: From WAL to Orchestrator Auto-Failover
JD Cloud Developers
JD Cloud Developers
Oct 22, 2026 · Databases

Database HA Deep Dive: Five Layers from WAL to Automated Failover

This article systematically explains database high availability through five layers: single-node crash recovery via WAL and two-phase commit, replication modes (async vs semi-sync) and RPO trade-offs, GTID-based global transaction identification for safe failover, fencing and PRS/ERS switching protocols to prevent split-brain, and Orchestrator's cross-check failure detection with probe-agent for automated failover.

Crash RecoveryFailoverGTID
0 likes · 28 min read
Database HA Deep Dive: Five Layers from WAL to Automated Failover
Random Bulletin
Random Bulletin
Oct 4, 2026 · Backend Development

From Hours to Minutes: Pre-Positioning Decisions to Slash Recovery Time at 10M QPS

This article decomposes recovery time into detection, decision, execution, and verification phases, showing how 10M QPS systems reduce recovery from hours to minutes by pre-positioning decisions at design time, bounding data loss via semi-sync replication, automating failover loops with fencing and quorum, and validating RTO through disciplined drills.

FailoverHigh AvailabilityRTO
0 likes · 34 min read
From Hours to Minutes: Pre-Positioning Decisions to Slash Recovery Time at 10M QPS
liandk
liandk
Sep 11, 2026 · Databases

MySQL Master-Slave Replication: Sync Principles, Delay Fixes, Read-Write Splitting & Failover

This article provides a comprehensive practical guide to MySQL master-slave replication, covering synchronization principles, three replication modes, delay causes and troubleshooting, read-write splitting implementation with common pitfalls, failover strategies, and five production pitfalls to avoid.

Database High AvailabilityDatabase ReplicationFailover
0 likes · 12 min read
MySQL Master-Slave Replication: Sync Principles, Delay Fixes, Read-Write Splitting & Failover
Aikesheng Open Source Community
Aikesheng Open Source Community
Aug 25, 2022 · Databases

Understanding Data Consistency in MySQL Semi‑Synchronous Replication and HA Failover

This article explains the principles of MySQL semi‑synchronous replication, analyzes how data consistency is maintained during high‑availability failover, presents detailed step‑by‑step transaction flow, discusses scenarios causing GTID divergence, and offers testing methods and remediation techniques for DBA practitioners.

DBAGTIDMySQL
0 likes · 14 min read
Understanding Data Consistency in MySQL Semi‑Synchronous Replication and HA Failover
Aikesheng Open Source Community
Aikesheng Open Source Community
Mar 19, 2019 · Databases

Root Cause Analysis of Slave IO Thread Hang in MySQL Semi‑Sync Replication with rpl_semi_sync_master_wait_for_slave_count=1

An in‑depth investigation reveals that when MySQL semi‑sync replication is configured with rpl_semi_sync_master_wait_for_slave_count=1, starting a second slave can cause the master’s dump thread to fail, leading to slave_io_thread stalls; the analysis includes reproduction steps, status checks, thread stack traces, and a patch using sched_yield to resolve the lock contention.

Dump threadMySQLSemi-sync Replication
0 likes · 8 min read
Root Cause Analysis of Slave IO Thread Hang in MySQL Semi‑Sync Replication with rpl_semi_sync_master_wait_for_slave_count=1
ITPUB
ITPUB
May 10, 2016 · Databases

Can MySQL Semi‑Sync Replication Keep Up? A Sysbench Performance Test

A performance test using sysbench on a dual‑node DL380 G7 MySQL 5.6 cluster shows that semi‑synchronous replication delivers roughly one‑third the TPS of asynchronous replication and highlights recovery and replication‑lag limitations that can be mitigated with sharding and parallel workers.

Database ReplicationMySQLSemi-sync Replication
0 likes · 6 min read
Can MySQL Semi‑Sync Replication Keep Up? A Sysbench Performance Test