You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.
At the point where a candidate becomes elected and initializes its matchIndex, it may already have entries in its log. If so, it should set its own matchIndex to a non-zero value, otherwise it will never count itself in the quorum for those entries.
The text was updated successfully, but these errors were encountered:
colin-scott
changed the title
Should
Shouldn't necessarily initialize matchIndex to -1
Aug 8, 2015
Well, arguably a bug: it decreases the fault-tolerance of the cluster by 1 for all terms where that leader is elected, i.e. progress won't be made if f-1 nodes fail
At the point where a candidate becomes elected and initializes its matchIndex, it may already have entries in its log. If so, it should set its own matchIndex to a non-zero value, otherwise it will never count itself in the quorum for those entries.
The text was updated successfully, but these errors were encountered: