Tagged articles
Split-Brain
20 articles · Page 1 of 1
A comprehensive guide to deploying Keepalived with Nginx for high availability, covering VRRP mechanics, health-check design, split-brain prevention, failover testing, and cloud-environment nuances, with concrete configs and verification steps.
FailoverHigh AvailabilityKeepalived
0 likes · 64 min read


liandkSep 30, 2026 · Cloud Native
This article provides a comprehensive troubleshooting guide for microservice registration discovery and gateway routing failures, covering 10 high-frequency Nacos faults, Eureka-specific issues, gateway routing problems, a step-by-step SOP, and production high-availability specifications to eliminate cascading outages.
CacheEurekaGateway
0 likes · 17 min read

This article explains HDFS High Availability architecture, detailing core components, the ZKFC-driven automatic failover process, split-brain causes like network partitions and GC pauses, and prevention mechanisms including JournalNode quorum, ZooKeeper locks, and fencing, plus production best practices.
FencingHDFSHigh Availability
0 likes · 7 min read

This article explains why Nacos CP mode can still experience split-brain despite using Raft, detailing four trigger scenarios (even-node partitions, GC pauses, cross-AZ latency, snapshot failures), three reasons CP appears like AP (client cache, read paths, module separation), and five practical fixes plus diagnostic commands.
CP modeConfiguration ManagementNacos
0 likes · 13 min read

This article provides a comprehensive production guide for Redis Cluster, covering cluster selection, hash slot principles, data skew solutions for big and hot keys, scaling strategies, master-slave replication latency handling, failure scenarios like split-brain, and a 7-point checklist with a real e-commerce case study.
Big KeyCaffeineData Skew
0 likes · 13 min read

This article explains why a single‑node Redis deployment is a single‑point‑of‑failure and walks through building a highly available Redis cluster using master‑slave replication, Sentinel monitoring and automatic failover, split‑brain prevention, production deployment guidelines, common pitfalls, and client‑side connection strategies.
ConfigurationFailoverHigh Availability
0 likes · 36 min read

This article explains the Redis split‑brain problem that can occur in master‑replica clusters, outlines the interview points interviewers look for, and provides a detailed solution using the min‑replicas‑to‑write (or min‑slaves‑to‑write) configuration to sacrifice write availability for data consistency, along with best‑practice recommendations and common pitfalls.
ConfigurationHigh AvailabilityInterview
0 likes · 12 min read

The article examines the two most dangerous production failures in Redis high‑availability—split‑brain and replication storm—explaining their causes, real‑world impact, and practical engineering safeguards such as write‑protection parameters, network isolation, backlog sizing, and cascading replication.
High AvailabilityRedisReplication Storm
0 likes · 7 min read

This article reveals three hard‑to‑detect pitfalls in Nginx + Keepalived high‑availability setups—split‑brain caused by network partitions, inadequate health‑check scripts, and unsafe configuration‑sync timing—provides real‑world incident examples, and offers complete, battle‑tested solutions with ready‑to‑use scripts.
Configuration SyncHigh AvailabilityKeepalived
0 likes · 16 min read

This guide explains the fundamentals of Keepalived, its key features, VRRP‑based high‑availability architecture, step‑by‑step installation and configuration of Keepalived and Nginx on master and backup servers, scripts for health checks, split‑brain causes and solutions, and Zabbix monitoring to detect and alert on HA failures.
KeepalivedSplit-BrainVRRP
0 likes · 46 min read

This article explains Redis split‑brain behavior, describing its definition, causes such as network failures and Sentinel elections, the resulting data loss during master‑slave switches, and practical prevention measures including quorum configuration, timeout tuning, network monitoring, proxy layers, and the min‑slaves‑to‑write and min‑slaves‑max‑lag settings.
High AvailabilityMaster‑SlaveSentinel
0 likes · 7 min read

This guide outlines practical methods to avoid split‑brain incidents in production HA clusters, including dual‑cable heartbeats, arbitration mechanisms, monitoring alerts, disk‑locking techniques, and a detailed keepalived‑based script for automated detection and recovery.
High AvailabilityKeepalivedOperations
0 likes · 10 min read


ITPUBJun 10, 2022 · Operations
This article explains the split‑brain phenomenon in distributed systems, illustrates how it can occur in Zookeeper clusters, and details Zookeeper's quorum‑based solutions—including majority voting, odd‑node deployment, and additional safeguards—to avoid split‑brain and ensure reliable leader election.
Leader ElectionSplit-Braindistributed systems
0 likes · 11 min read

This article explains why data loss can occur in Redis master‑slave clusters due to split‑brain scenarios, outlines step‑by‑step troubleshooting methods—including checking replication lag, analyzing client logs, and monitoring resource usage—and recommends configuration settings such as min‑slaves‑to‑write and min‑slaves‑max‑lag to prevent the issue.
ConfigurationMaster‑SlaveRedis
0 likes · 8 min read

This article explains the split‑brain phenomenon in distributed clusters, uses Zookeeper as a case study to illustrate how network partitions can create multiple leaders, and details Zookeeper's majority‑quorum mechanism, node count considerations, and common strategies for avoiding split‑brain scenarios.
Leader ElectionSplit-BrainZooKeeper
0 likes · 13 min read

This article explains why Redis can lose data during asynchronous master‑slave replication failures or split‑brain partitions, and shows how configuring min‑slaves‑to‑write and min‑slaves‑max‑lag, along with client‑side fallback strategies, can greatly reduce the risk of loss.
ClusterHigh AvailabilityRedis
0 likes · 5 min read

This article provides a comprehensive overview of the Raft consensus algorithm, detailing node roles (follower, candidate, leader), the leader election process, mechanisms ensuring cluster consistency, handling of node failures, and strategies for resolving split‑brain scenarios in distributed systems.
ConsensusConsistencyLeader Election
0 likes · 11 min read

This article explains why ZooKeeper clusters should use an odd number of nodes, how the majority quorum mechanism avoids split‑brain scenarios, and outlines practical solutions such as quorums, redundant communication, fencing, arbitration, and disk‑lock techniques to ensure reliable distributed coordination.
Split-BrainZooKeeperdistributed systems
0 likes · 14 min read

This article explains the causes of ZooKeeper split‑brain situations, why odd‑numbered node deployments are preferred, how the quorum (majority) rule prevents split‑brain, and outlines practical methods such as quorum configuration, redundant communication, fencing, and pause‑before‑failover to handle and avoid the issue.
High AvailabilitySplit-Braincluster management
0 likes · 13 min read


ITPUBNov 26, 2015 · Operations
This article explains what split‑brain is in high‑availability systems, compares arbitration and fencing methods, evaluates client‑routing options without fencing devices, discusses data‑loss risks during failover for PostgreSQL and MySQL, and provides concrete implementation guidance using Pacemaker and Corosync.
FencingPacemakerSplit-Brain
0 likes · 10 min read
