These are chat archives for RBMHTechnology/eventuate
Global-scale event sourcing and event collaboration with causal consistency
replicaVersionVectorsaround given that those are just cached versions of the version vectors of remote logs. Shouldn't the remote log already have this information?
Thanks for your help Volker.
Shouldn't the remote log already have this information
This is true but only for dense replication networks, not for sparse like
I've tried to get the information that I need from
ReplicationWrites but without success, I mean that C and B get the CTVV from each other through the
ReplicationWrite sent by A but it doesn't work.
ReplicationReadand this worked except for sparse networks.
ReplicationProtocolunchanged and send scheduled
Replicator(with a default of 1 minute perhaps).