open atlas
↑ Back to track
Distributed Systems DIST · 02 · 08

Raft: free-recall review

Free-recall prompts across the Raft unit. Answer each from memory first, then reveal the model answer and compare against the mechanism the lessons taught.

DIST Senior ◷ 14 min
Level
FoundationsJuniorMiddleSenior

Retrieval beats re-reading. For each prompt, reconstruct the full mechanism from memory — out loud or on paper — before you open the model answer. The effort of recall is what makes the safety argument stick.

Goal

Reconstruct the unit’s spine without looking back: the quorum-overlap safety argument, what “committed” means, why the voting rule preserves history, how linearizable reads avoid a log write, and why membership change needs joint consensus.

Recall before you leave
  1. 01
    Why does requiring a majority quorum for both elections and commits prevent split brain, and why specifically a majority rather than any fixed-size group?
  2. 02
    What does 'committed' mean in Raft, and why is a single-node fsync not enough?
  3. 03
    How does the RequestVote log-completeness rule combine with quorum overlap to give Leader Completeness, and what is the extra current-term commit caveat?
  4. 04
    Contrast ReadIndex and lease reads for serving linearizable reads, and state the correctness precondition that makes lease reads risky.
  5. 05
    Why does changing cluster membership require joint consensus, and what does the joint phase actually enforce?
  6. 06
    What is the minimum viable Raft dashboard, and what root cause does each metric point to?
Recap

If you could rebuild each answer from memory you hold the unit’s spine: majority quorum forces overlap, which makes a committed (majority-persisted) entry survive every leader change; the log-completeness vote plus that overlap gives Leader Completeness, with the current-term commit rule closing the figure-8 hole; ReadIndex and lease reads serve linearizable reads without a log write — lease reads trading an NTP correctness precondition for sub-millisecond latency; and joint consensus keeps membership change from splitting the cluster. Watch five metrics, and remember that real incidents nearly always trace to bypassed membership, disabled pre-vote, or a slow disk.

Something unclear?

Ask a question about this lesson. Questions are anonymous and go straight to the author to make the lesson better.

shortcuts expand
search
K
prev piece
k
next piece
j
cycle tier
t
this menu
?
sources3
expand
  1. 01
  2. 02
  3. 03

Trademarks belong to their respective owners. Editorial reference only.