Re: [infinispan-dev] X-datacentre replication: design suggestions
I have two transactions, run in sequence:
- TX1 updates A
- TX2 deletes A
If you send them both in async to the other datacenter, you'll have
to
make sure they are not reordered. I know JGroups can provide that
guarantee, just wondering if it's the plan to do this via JGroups, or
if we have an own buffer that we can still guarantee the order, or
even better merge changes on the same keys like we do with the async
CacheStore.
Thanks for the clarification, Sanne.
Tx1 needs to place the info into the bridge's async queue *before* releasing the lock.
Commit is a good fit, as durign commit the lock is stil held. Then the bridge must make
sure that it doesn't reorder elements in the queue.