Hi, Does H2 ensure that replicas are in a consistent state when clustering > is enabled? I don't see any code ensuring that transactions will be > executed in the same order at the different replicas. Am I missing > something? >
I think you are right. It is possible that a transaction from one client 'overtakes' the transaction from another client, as follows: client 1: update first cluster instance client 2: update first cluster instance client 2: update second cluster instance client 1: update second cluster instance I don't know how common this is in practice, but in theory it's possible. I don't know currently what's the best / easiest way to solve this problem. One solution is, if the first cluster instance would send the changes to the other cluster instances (replicas). More and more problems are found in the cluster feature of H2... I will document the limitations and mark the feature are experimental. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
