Quantcast
Channel: StackExchange Replication Questions
Viewing all articles
Browse latest Browse all 17268

RAFT election restrictions

$
0
0

I'm learning Raft from scratch with the Raft paper, and I don't get to understand the leader election process. I read in 5.4.1 that a leader needs to have in its log all the committed entries of the cluster:

Raft uses a simpler approach where it guarantees that all the committed entries from previous terms are present on each new leader from the moment of its election, without the need to transfer those entries to the leader.

Raft uses the voting process to prevent a candidate from winning an election unless its log contains all committed entries.

But later on, it is said that a candidate holds all the committed entries if it is at least as up-to-date as any other log in the majority. And the mechanism to determine this up-to-date is comparing the index and term of the last entries. The log with the higher term on the last entry will be more up-to-date.

Couldn't that lead to a situation in which a leader was elected without all previous committed entries? For instance:

enter image description here

In this case, if server 4 failed, server 2 could become leader, since it has an entry with a bigger term than the majority. But it wouldn't have in its log the two committed entries from term 2. Is that right? I am misunderstanding something but I can get what it is...


Viewing all articles
Browse latest Browse all 17268

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>