Split-brain (computing)
![]() | This article or section possibly contains original synthesis. Source material should verifiably mention and relate to the main topic. (December 2011) |
This article needs additional citations for verification. (December 2011) |
Split-brain is a term in computer jargon, based on an analogy with the medical Split-brain syndrome. It indicates data inconsistencies originating from the mainenance of two separate data sets with overlap in scope.
Typical usage of the jargon term is when internal and external Domain Name Services (DNS) for a corporate network are not communicating, so that separate DNS name spaces are to be administrated for external computers and for internal ones. This requires a double administration, and if there is domain overlap in the computer names, there is a risk that the same fully qualified domain name (FQDN), may ambiguously occur in both name spaces referring to different computer IP addresses[1].
High-availability clusters usually use a heartbeat private network connection which is used to monitor the health and status of each node in the cluster. One subtle, but serious condition every clustering software must be able to handle is split-brain.
Split-brain occurs when all of the private links go down simultaneously, but the cluster nodes are still running.
If that happens, each node in the cluster may mistakenly decide that every other node has gone down and attempt to start services that other nodes are still running. Having duplicate instances of services may cause data corruption on the shared storage.
This problem can lead to data inconsistency. To prevent it computers should use redundant communications and fall down to an auto-fencing mode when the peers look like they are down. This means they should run in a limited mode to prevent data destruction
References
- ^ Windows Server 2008 Active Directory, Configuring (2nd Edition), Holme, Ruest, Ruest, Kellington, ISBN 978-0-7356-5193-7