Raft
One Leader per Term
Majority voting prevents two leaders in one term.
One leader per term
A failed election can leave a term with no leader. A later timeout starts a new term and can elect one. Note: the timeline shows the no-leader gap before the later leader.
No majority first
The trace ultimately has 1 leader, and that leader appears in term 2. Note: the earlier term has no leader in the render.
a simplified Raft over a tiny cluster: terms, votes, leader election, and the term-restricted commit rule are exact on these traces; the full safety proof, membership changes, snapshotting, log compaction, and real RPC/timing are beyond these traces - no product claims.
Next term elects
The successful election tally has 3 votes. Note: the new term, not the failed term, installs the leader.
a simplified Raft over a tiny cluster: terms, votes, leader election, and the term-restricted commit rule are exact on these traces; the full safety proof, membership changes, snapshotting, log compaction, and real RPC/timing are beyond these traces - no product claims.
Summary
One-leader-per-term comes from majority voting over ordered terms. Note: this is simplified Raft; the full safety proof, membership changes, snapshots, and real timing are beyond these traces.