Hi, > In my case, for instance, reading from > the local node would be the most natural thing to do.
Sure. There is a feature request: "Support mixed clustering mode (one embedded, others in server mode)". > 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? No. Could you try to find out what is going on? (maybe debugging will help, or use java -Xrunhprof:cpu=samples ...). If not, could you create a simple test case so I can reproduce the result? Is it reproducible on a single machine? > 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 that detection should be automatic (so that you don't need to know which one is the local node). That may actually be almost as easier to implement manual configuration. 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.
