Re:Raft: Understandable Distributed Consensus
by DanWaterworth on Friday September 05, 2014 @07:19AM
(#8273265)
If an entry has been replicated to a majority of followers, then the new leader is guaranteed to have that entry and therefore it won't be rolled back.
[ Parent
| on HN ]
Re:Raft: Understandable Distributed Consensus
by regularfry on Friday September 05, 2014 @09:12AM
(#8273652)
How does the new leader know it went to a majority? The only entity which could confirm that is the old leader.
Re:Raft: Understandable Distributed Consensus
by Muzzaf on Friday September 05, 2014 @09:50AM
(#8273833)
That is correct. The solution to this is given in section 5.4.1 (election restriction), section 5.4.2 (Committing entries from previous terms) and section 8 (Client interaction) of the Raft paper.
Roughly, a newly elected leader will have all committed entries (guaranteed by the "election restriction", 5.4.2) but it does not know precisely which are committed. The new leader will commit a no-op log entry (section 8) and after it has received replies from a majority of the cluster it will know which entries have already been committed.
Re:Raft: Understandable Distributed Consensus
by regularfry on Friday September 05, 2014 @10:16AM
(#8273957)
Ooh, thanks. The no-op commit is particularly interesting.