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
In #110, we made some minor changes to snapshot handling, which removed the main use of Progress.PendingSnapshot. As described in #110 (comment), we should now be able to remove PendingSnapshot completely, and take the opportunity to clean up some of the related state transitions.
Also, as described in cockroachdb/cockroach#87583 and #110 (comment), we should modify ReportSnapshot() and MsgSnapStatus to take the index of the applied snapshot -- in the common case, this will be the same as that in MsgSnap, but complex systems (e.g. CockroachDB) may generate and apply snapshots at a different index than that requested by Raft (e.g. to send snapshots from a follower in the same region), and reporting back the actual index would simplify the logic and e.g. allow updating Match and transitioning directly to StateReplicate in this case.
These are all breaking changes to public APIs, so would have to be done for 4.0. There are possibly other related cleanups that could be made as well.
@pav-kv@ahrtr Please add any further ideas and context as needed.
The text was updated successfully, but these errors were encountered:
In #110, we made some minor changes to snapshot handling, which removed the main use of
Progress.PendingSnapshot
. As described in #110 (comment), we should now be able to removePendingSnapshot
completely, and take the opportunity to clean up some of the related state transitions.Also, as described in cockroachdb/cockroach#87583 and #110 (comment), we should modify
ReportSnapshot()
andMsgSnapStatus
to take the index of the applied snapshot -- in the common case, this will be the same as that inMsgSnap
, but complex systems (e.g. CockroachDB) may generate and apply snapshots at a different index than that requested by Raft (e.g. to send snapshots from a follower in the same region), and reporting back the actual index would simplify the logic and e.g. allow updatingMatch
and transitioning directly toStateReplicate
in this case.These are all breaking changes to public APIs, so would have to be done for 4.0. There are possibly other related cleanups that could be made as well.
@pav-kv @ahrtr Please add any further ideas and context as needed.
The text was updated successfully, but these errors were encountered: