Tagged articles
Semi-Sync
13 articles · Page 1 of 1
This article details a five-layer database high availability architecture: single-node crash recovery via WAL and two-phase commit, asynchronous and semi-synchronous replication trade-offs, GTID-based global transaction identification for seamless failover, fencing mechanisms to prevent split-brain, and Orchestrator with probe-agent for automated failure detection and failover execution.
Crash RecoveryFailoverFencing
0 likes · 26 min read

The article examines common MySQL replication failures, explains why traditional position‑based replication is insufficient, and walks through a step‑by‑step evolution from file/position to GTID, asynchronous to semi‑synchronous, single‑threaded to parallel apply, culminating in a production‑grade architecture that achieves near‑zero data loss.
GTIDHigh AvailabilityMySQL
0 likes · 35 min read

The article dissects a high‑traffic flash‑sale interview question—how to guarantee zero order loss at 100,000 TPS when the master MySQL instance fails—by explaining the underlying performance‑consistency conflict, the three skills interviewers assess, and presenting five concrete, code‑driven solutions ranging from MySQL parameter tuning to semi‑sync replication, local message tables, group replication, and Redis‑Kafka traffic shaping.
Data ConsistencyGroup ReplicationKafka
0 likes · 28 min read

This article outlines MySQL’s three primary replication architectures—async, semi‑sync, and full‑sync—detailing their mechanisms, typical topologies, performance trade‑offs, and suitable scenarios such as read‑heavy web services, high‑availability setups, and strict consistency requirements like financial transactions.
Database ArchitectureMySQLReplication
0 likes · 4 min read

This article provides a comprehensive overview of MySQL master‑slave replication, explaining its core mechanisms, the push‑pull hybrid model, replication modes (asynchronous, full‑sync, semi‑sync), binlog formats, and practical strategies to reduce replication lag caused by large transactions, server load, and network constraints.
MySQLReplicationSemi-Sync
0 likes · 9 min read

This tutorial walks through preparing the Linux environment, installing MySQL 5.7, configuring master and slave servers, creating replication users, verifying synchronization, troubleshooting common issues, and applying advanced options such as GTID and semi‑synchronous replication, all with complete command examples.
ConfigurationGTIDLinux
0 likes · 10 min read

This article thoroughly examines MySQL replication, detailing binlog formats, event types, replication workflows, semi‑synchronous and parallel replication techniques, performance benchmarks, and practical implementation steps such as fake‑slave registration and connection‑pool enhancements, while illustrating each concept with concrete examples and code snippets.
High AvailabilityMySQLReplication
0 likes · 30 min read


ITPUBNov 6, 2022 · Databases
The article explains why a recent write may be invisible when reading from a MySQL replica, analyzes the replication threads and latency causes, and presents practical solutions such as forcing master reads, lag detection, semi‑sync mode, and GTID‑based waiting, with examples from Sharding‑JDBC, MyCat and MaxScale.
Database MiddlewareGTIDMaster‑Slave
0 likes · 10 min read

This article explains MySQL replication fundamentals, binary log mechanics, master‑slave roles, configuration steps, and the various replication types—including asynchronous, semi‑synchronous, multi‑source, and delayed replication—while providing practical commands and code examples for reliable high‑availability setups.
Binary LogDelayed ReplicationMySQL
0 likes · 14 min read

This article presents a detailed experiment comparing graceful and kill‑9 shutdown methods on a MySQL 5.7 semi‑synchronous master‑slave cluster, analyzes their impact on data consistency, and outlines the official shutdown sequence with practical observations and recommendations for production environments.
MySQLReplicationSemi-Sync
0 likes · 12 min read


ITPUBAug 19, 2021 · Databases
This article explains why a single MySQL instance becomes insufficient as data volume and concurrency grow, and walks through master‑slave replication, asynchronous and semi‑synchronous modes, group replication, and various high‑availability solutions such as MHA, MySQL InnoDB Cluster, and Orchestrator, while also covering read/write splitting techniques and practical implementation tips.
Group ReplicationMaster‑SlaveMySQL
0 likes · 20 min read

When using MySQL 5.7 with rpl_semi_sync_master_wait_for_slave_count=1, starting a second semi‑sync replica often causes the slave_io_thread to stall because the master cannot launch the corresponding dump thread, a bug that was later fixed in MySQL 5.7.23.
MySQLSemi-Syncslave_io_thread
0 likes · 8 min read

A practical benchmark on three identical servers shows MySQL Group Replication achieving higher TPS than Semi‑Sync despite larger network traffic, and explains how Paxos‑based parallel log transmission gives it an edge over the single‑threaded Semi‑Sync approach.
Database ReplicationGroup ReplicationMySQL
0 likes · 6 min read
