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.
In AppendEntries.apply, if a batch is empty (e.g. because the follower is completely caught up and we're sending a heartbeat), the message is sent with prevLogTerm 1 and prevLogIndex 1. This is not necessarily correct; the numbers should be based off of what is actually at the end of the log.
The text was updated successfully, but these errors were encountered:
Tested by fuzz testing -- I verified that under non-failing scenarios, this behaves correctly at each step of the execution when replicated two client commands.
In
AppendEntries.apply
, if a batch is empty (e.g. because the follower is completely caught up and we're sending a heartbeat), the message is sent withprevLogTerm
1 andprevLogIndex
1. This is not necessarily correct; the numbers should be based off of what is actually at the end of the log.The text was updated successfully, but these errors were encountered: