Hi, > My questions concerns failover management. > First of all, is there supplementary documentation about this feature > not included in H2 web-site?
No. > When A & B are restarted, is there a way to automatically detect > databases states? (something like: A is KO, B is OK) You can't connect to them in cluster mode, so you know something is wrong. See also the documentation "Detect Which Cluster Instances are Running" > After running the above scenario, when I tried to open B with the file > protocol (“jdbc:h2:file:./nodeB/test”) => OK (db is successfully > opened) Sure, but if you want to use the cluster mode then you are not supposed to do that. Instead, use the cluster URL. > Then, can I consider that opening a database with the file protocol is > a relevant test to check its state? I guess no, but... Yes. > What are the expected operations to come back to a normal situation? Use the CreateCluster tool, as documented. > Is there an alternative to delete database A and reconstruct the > cluster? (some kind of partial resynchronization). No. > Finally, I guess that for automatic recovery I need to write code on > top of H2. Yes. > Is there any example of such management? In my view, a crash of a computer is something the admin should notice, and then he should manually run the CreateCluster tool to reconstruct the cluster. The current cluster mechanism of H2 is not meant for very large numbers of computers (like Google data centers), but it is meant to improve availability. 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.
