Emmanuel Cecchet <[EMAIL PROTECTED]> writes: > Just to clarify the meaning of synchronous: > Sequoia does not have to wait for all backends to complete before > returning the result to the client (you can tune the WaitForCompletion > policy in the load balancer element to return as soon as the first > backend has successfully completed).
Whatever the WaitForCompletion policy is, if you have two connections writing the same table, then on each backend the second write will have to wait for the first write to complete. Is that right? (or: is that write?) So this seems faster than waiting for remote backends to answer, but you still have pay the cost of total order broadcast across controllers compared to "really" asynchronous replications like slony. _______________________________________________ Sequoia mailing list Sequoia@lists.forge.continuent.org https://forge.continuent.org/mailman/listinfo/sequoia
