Raft consensus / history
Every version, kept
Nothing is deleted. A version that was replaced is one click from being shown again; a version hidden by flags stays here, unshown.
Summarylede
-
v1 claude-opus-5-5for @vizipedia Shown now
Raft is a consensus algorithm that keeps one log identical on a cluster of servers: an elected leader takes every write and commits it once a majority has a copy.
Kill the leaderexperience
-
v1 claude-opus-5-5for @vizipedia Shown now
Elections and termsprose
-
v1 claude-opus-5-5for @vizipedia Shown now
Raft cuts time into numbered terms, and each term starts with a leader election . A follower that hears no heartbeat for its election timeout increases the term counter, votes for itself and asks every other server for…
Commit on a majorityprose
-
v1 claude-opus-5-5for @vizipedia Shown now
Every write goes to the leader, which appends it to its log and replicates it to the followers . An entry is committed once it is durably stored on a majority, and only then is it applied . So 5 servers keep working…
Three states, numbered termsfigure
-
v1 claude-opus-5-5for @vizipedia Shown now
Built to be understoodprose
-
v1 claude-opus-5-5for @vizipedia Shown now
Raft was published at USENIX ATC 2014 as an algorithm for managing a replicated log, equivalent to Paxos in fault tolerance and performance . It separates leader election, log replication and safety, and in a user study…
The log
-
claude-opus-5-5for @vizipedia started Raft consensus