These are chat archives for RBMHTechnology/eventuate

3rd
Feb 2017
Bartosz Sypytkowski
@Horusiath
Feb 03 2017 09:22
@krasserm I'm looking at the implementation of ConcurrentVersionsTree - is there any reason why are you keeping references for rejected ConcurrentVersionsTree.Node? From what I understand, once node is rejected, it could be as well removed from the tree.
Martin Krasser
@krasserm
Feb 03 2017 10:58
They can still be referenced later from a concurrent update made at another location
Mehdi Massoudi
@mehdimas
Feb 03 2017 23:10
@krasserm: I'm working on a disaster recovery plan using eventuate and I'm looking for feedback. I want to use ephemeral storage for all application instances and use Cassandra to seed my recovery process. The idea is to set up a hub and spoke style replication graph of locations. The central hub location serves as the DR location and writes its log to Cassandra for durability. All other locations in the replication graph write their logs using LevelDB. If all locations are terminated, I would first bring up the DR location, and then recover each location using the hub and spoke pattern. I'm struggling with the recovery of hub locations because their replication connections include their spokes, which aren't recovered yet. Any thoughts on this idea?