I understand your point. The question is how do we get a high available system with acceptable performance. In my case, for instance, reading from the local node would be the most natural thing to do.
Also related to the performance of this read algorithm, I made a small test that produced troublesome results. Maybe I'm doing something wrong. In a cluster with five nodes, a select takes 50 ms, which is great. But when I kill the node from which the read is done, it jumps to an average of 3500ms. Does that match your results? > Not desired for a high performance cluster, I agree. > > I will add a feature request to support reading from random node. > That would be nice. What about adding a URL param that allows H2 users to specify which node to read from? Something like: jdbc:h2:tcp://address1,address2,address3,address4;READ_FROM=3 I think this would be generic enough to meet different read algorithms. It would allow me to read from the local node, allow other people to read from a single node, and still allow those who want to read from random nodes to be able to do so. -- 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.
