🔒 Paid

Split-Brain Incident

A network partition has severed connectivity between Region A and Region B. Per-account writes must never be accepted by more than one region at the same time — a divergent or conflicting write landing during the partition is a critical data-integrity incident, regardless of how healthy write availability looks in either region individually. Restore a single, unambiguous write authority across the cluster, and decide how any writes accepted during the split should be reconciled once connectivity returns.

Difficulty
Staff
Expected Time
~20 min
Category
Distributed Systems

Skills

  • Recognizing when customer-facing availability conceals a correctness failure
  • Distinguishing a structural quorum fix from a manually-achieved safe state
  • Reasoning about fencing the correct side of a partition
  • Deciding a reconciliation policy for divergent writes after connectivity returns

System Architecture

  • Region A
  • Distributed Coordinator
  • Region B

This is a Pro scenario. Upgrade to Pro to unlock it.

Upgrade to ProBack to Incidents