BestHub
Sign in
Tagged articles

split-brain

18 articles · Page 1 of 1
liandk
liandk
Sep 30, 2026 · Cloud Native

Microservice Registration & Gateway Fault Troubleshooting: Nacos/Eureka Heartbeat, Jitter, Routing Failures, Avalanche Solutions

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.

EurekaNacoscache
0 likes · 17 min read
Microservice Registration & Gateway Fault Troubleshooting: Nacos/Eureka Heartbeat, Jitter, Routing Failures, Avalanche Solutions
Programmer1970
Programmer1970
Aug 28, 2026 · Cloud Native

Nacos CP Mode Still Has Split-Brain? 4 Scenarios Where Raft Fails

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 modeNacosRaft
0 likes · 13 min read
Nacos CP Mode Still Has Split-Brain? 4 Scenarios Where Raft Fails
Yumin Fish Harvest
Yumin Fish Harvest
Jul 7, 2026 · Databases

Redis High‑Availability Deep Dive: Master‑Slave Replication, Sentinel, and Split‑Brain Protection

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.

ConfigurationFailoverRedis
0 likes · 36 min read
Redis High‑Availability Deep Dive: Master‑Slave Replication, Sentinel, and Split‑Brain Protection
Java Architect Handbook
Java Architect Handbook
Jan 28, 2026 · Databases

How to Prevent Redis Split‑Brain Disasters with min‑replicas‑to‑write

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.

ConfigurationRedisdistributed systems
0 likes · 12 min read
How to Prevent Redis Split‑Brain Disasters with min‑replicas‑to‑write
MaGe Linux Operations
MaGe Linux Operations
Aug 3, 2025 · Operations

Avoid 3 Hidden Nginx+Keepalived HA Pitfalls That 90% of Ops Encounter

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 SyncKeepalivedNginx
0 likes · 16 min read
Avoid 3 Hidden Nginx+Keepalived HA Pitfalls That 90% of Ops Encounter
MaGe Linux Operations
MaGe Linux Operations
Nov 16, 2024 · Operations

How to Build Keepalived High‑Availability Nginx with VRRP and Zabbix Monitoring

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.

KeepalivedVRRPload balancing
0 likes · 46 min read
How to Build Keepalived High‑Availability Nginx with VRRP and Zabbix Monitoring
IT Services Circle
IT Services Circle
Oct 4, 2024 · Databases

Understanding Redis Split‑Brain: Causes, Data Loss, and Prevention Strategies

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.

Master‑SlaveSentineldatabase
0 likes · 7 min read
Understanding Redis Split‑Brain: Causes, Data Loss, and Prevention Strategies
ITPUB
ITPUB
Jun 10, 2022 · Operations

How Zookeeper Prevents Split‑Brain Failures in Distributed Clusters

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 Electiondistributed systemsquorum
0 likes · 11 min read
How Zookeeper Prevents Split‑Brain Failures in Distributed Clusters
Ziru Technology
Ziru Technology
Apr 8, 2022 · Databases

How to Diagnose and Prevent Split-Brain Data Loss in Redis Master-Slave Clusters

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.

ConfigurationData lossMaster‑Slave
0 likes · 8 min read
How to Diagnose and Prevent Split-Brain Data Loss in Redis Master-Slave Clusters
Senior Brother's Insights
Senior Brother's Insights
Jul 28, 2021 · Operations

How Zookeeper Prevents Split‑Brain: Inside Quorum‑Based Leader Election

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 ElectionZooKeepercluster-management
0 likes · 13 min read
How Zookeeper Prevents Split‑Brain: Inside Quorum‑Based Leader Election
Top Architect
Top Architect
Feb 21, 2021 · Fundamentals

Understanding the Raft Consensus Algorithm: States, Leader Election, Consistency, and Split‑Brain Handling

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.

ConsensusLeader ElectionRaft
0 likes · 11 min read
Understanding the Raft Consensus Algorithm: States, Leader Election, Consistency, and Split‑Brain Handling
Efficient Ops
Efficient Ops
Jan 5, 2021 · Operations

How to Prevent ZooKeeper Split‑Brain: Best Practices and Fault‑Tolerance Strategies

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.

ZooKeeperdistributed systemsfault tolerance
0 likes · 14 min read
How to Prevent ZooKeeper Split‑Brain: Best Practices and Fault‑Tolerance Strategies
Architecture Digest
Architecture Digest
Nov 21, 2020 · Operations

Understanding and Handling ZooKeeper Split‑Brain Issues

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.

cluster-managementhigh availabilityquorum
0 likes · 13 min read
Understanding and Handling ZooKeeper Split‑Brain Issues
ITPUB
ITPUB
Nov 26, 2015 · Operations

How to Prevent Split‑Brain in HA Clusters: Arbitration, Fencing, and Practical Strategies

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.

FencingPacemakerarbitration
0 likes · 10 min read
How to Prevent Split‑Brain in HA Clusters: Arbitration, Fencing, and Practical Strategies