Raft Consensus with a Minority of Nodes
The article discusses a modification to the Raft consensus protocol that allows progress with fewer than a majority of nodes. This adjustment is based on mathematical principles similar to those found in the card game Spot It! The author explains the importance of overlapping nodes in maintaining consistency and fault tolerance within the Raft framework.
- ▪Raft is a consensus protocol designed to manage a replicated log across a cluster of nodes.
- ▪The protocol requires a majority of nodes to commit changes, ensuring fault tolerance and consistency.
- ▪The modification allows for progress even with a minority of nodes, provided certain constraints are met.
Opening excerpt (first ~120 words) tap to expand
Raft Consensus with a Minority of Nodes By Rohan Padhye (@moarbugs on X) tl;dr — This post describes a (wacky) modification to the Raft consensus protocol such that progress can be made even if fewer than a majority of nodes are actively participating, given some constraints on exactly which minority of nodes are active. The math behind this comes from the same place as the card game Spot It! (Dobble). Raft Consensus Basics Raft is a consensus protocol for managing a replicated log across a cluster of nodes. Its key goals are: (1) maintain a consistent replicated log of state transitions, (2) tolerate node failures, and (3) ensure a single leader coordinates all changes while multiple followers replicate.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Padhye.
Discussion
0 commentsMore from Padhye
