Hi, The clustering mechanism is mainly for high availability and not for high performance. See http://www.h2database.com/html/advanced.html#clustering
> Essentially, the second node rearranges the order of servers in the URL so > that its address is the first. This doesn't seem to be loved by H2. Yes, this is not supported. The problem is: if two clients use a different order, then updates would be written in different order, which could lead to deadlocks. Reading from a server would be problematic as well in some cases where writes and reads are mixed. > It suggests to me that in a cluster of 10 nodes for instance, 9 of them will > be performing read-only queries on the same remote node, which I assume was > not not the desired behavior. Not desired for a high performance cluster, I agree. I will add a feature request to support reading from random node. 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=.
