Hi, I have two nodes in a cluster. When I connect to it from the VM of the first node (62.165.121.14), everything is fine; but when i connect to it from the VM of the second node (211.245.193.235), I get the exception:
Clustering error - database currently runs in cluster mode, server list: "' 62.165.121.14:8803,211.245.193.235:8803' The URL I use to connect from the first node is: tcp://62.165.121.14:8803, 211.245.193.235:8803/test The URL used to connect from the 2nd node is: tcp://211.245.193.235:8803, 62.165.121.14:8803/test. 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. I thought this rearranging is necessary because the documentation says "Read-only queries are only executed against the first cluster node, but all other statements are executed against all nodes." If this is statement is true, isn't the constraint that always the same URL be used to connect to the cluster (independently from where the request is made) counter-productive? 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. I'm sure I am missing something here. Please help me figure it out. Thanks, Merkel -- 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=.
