Skip to content

CONCEPT Cited by 1 source

Split-brain

Split-brain is the failure mode in which two (or more) nodes each believe they have authoritative ownership of the same resource — typically a key, partition, or leadership role. Or the dual: no node thinks it owns the resource, and requests drop silently. Both shapes appear under partition/crash/intermittent-failure scenarios when ownership is decided without a coordinator.

Where it shows up in sharding

Static-sharding schemes compute key → node independently in each client (concepts/static-sharding). When pods crash or become intermittently unresponsive, clients can arrive at inconsistent views of membership:

  • Two pods own the same key → writes may conflict or be silently lost; cache coherence breaks.
  • No pod owns the key → customer traffic is dropped entirely.

Static consistent-hashing has no pathway to prevent either outcome because there's no authoritative record of "who owns what right now" — just whichever clients each client sees as alive.

Mitigations

Trade-off with eventual consistency

systems/dicer chose concepts/eventual-consistency of its Assignment publication: pods and clients may briefly hold different views of ownership during transitions. The system is designed so such transient disagreement doesn't corrupt state — but it explicitly does not provide the exclusive-ownership guarantee that leases / consensus would. Applications that need that guarantee layer it on top (or use a different system).

Seen in

Last updated · 200 distilled / 1,178 read