Notesreplication🌱 seedling

Sloppy Quorum

Also: Hinted Handoff · Hint

When a key's home replicas are unreachable, accept the write on other healthy nodes, which keep it with a hint naming the intended owner and hand it off later. Writes stay available; quorum overlap is gone until handoff.

Why it exists

A network fault can cut a client off from most of a key's n home replicas. A strict quorum would reject the write; an "always writeable" store would rather put it somewhere.

How it works

  • Write to the first n healthy nodes in the key's preference list, even if some aren't home replicas.
  • A stand-in stores the write plus a hint ("this belongs to B").
  • Hinted handoff: when B is reachable again, the stand-in forwards the write and drops its copy.
  • Until then, a read of r home replicas may not include any replica with the write.

Trade-offs

Gains Costs
writes succeed if any w nodes are reachable w + r > n no longer implies overlap
fast catch-up for short outages hints are best effort; long outages need repair

In practice

  • Dynamo introduced it as a deliberate availability choice.
  • Cassandra keeps hinted handoff without the sloppy quorum: the consistency level counts acknowledgements from the key's own replicas, and only ANY accepts a stored hint in place of one. Coordinators keep hints for a down replica for up to max_hint_window (3 hours by default); beyond that, only read repair or anti-entropy repair brings it back in sync.

Pitfalls

  • Treating hints as a durability guarantee. They're an optimisation; scheduled Anti-Entropy is still required.

Recall

These cards are also in your review deck, scheduled with spaced repetition.