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
If I am reading the paper (Efficient Reconciliation and Flow Control for Anti-Entropy Protocols) right, the history of a certain key is not guaranteed to sync completely, i.e., in some edge-cases some old values/versions are omitted.
E.g. Paper p. 3 figure 1 and
A remarkable property of Scuttlebutt is that the gossip ex- change between two participants is not designed to eliminate all differences between the two participants, even if there is sufficient room in the gossip messages.
Have you made some adjustments to the scuttlebutt approach to guarantee full-history sync, does the scuttlebutt/events omit events, or do I get the paper wrong?
Just want to now, what to expect from scuttlebutt/events 😉
Thanks
The text was updated successfully, but these errors were encountered:
Well I think the heart of the protocol is really about log replication.
it's the handshake that is the important thing. When they talk about 'old values'
that is in a layer on top of that.
The way the use it,
they forget information that isn't relavant - which is how scuttlebutt/model works,
but scuttlebutt/events doesn't forget anything.
If I am reading the paper (Efficient Reconciliation and Flow Control for Anti-Entropy Protocols) right, the history of a certain key is not guaranteed to sync completely, i.e., in some edge-cases some old values/versions are omitted.
E.g. Paper p. 3 figure 1 and
Have you made some adjustments to the scuttlebutt approach to guarantee full-history sync, does the scuttlebutt/events omit events, or do I get the paper wrong?
Just want to now, what to expect from scuttlebutt/events 😉
Thanks
The text was updated successfully, but these errors were encountered: