Thanks, Thomas, for the answers. Am 10.05.2011 19:30, schrieb Thomas Mueller: > Currently, rebuilding the cluster is a manual step. After re-building, > all clients need to re-connect. I'm not sure if you read the > documentation: http://h2database.com/html/advanced.html#clustering "The > cluster can be re-created using the CreateCluster tool without stopping > the remaining server. Applications that are still connected are > automatically disconnected, however when appending ;AUTO_RECONNECT=TRUE, > they will recover from that."
Yes, I read that (and assume I understood :-) I was thinking about building a cluster control program that would automate the cluster rebuild without any human intervention. Yes, I know, in many cases you would not want such an automatism because there is so much that can go wrong... However, I need to deal with customers that don't want to control their database manually (in fact they don't want to care about these 'details'). In the case I have described, that system could end up in a situation where one client (that was connected when cluster frgamentation occured) works on only one database while another client (that did connect when network connectivity was up again) works on both of them ... with nobody even noticing that they are running into more and more inconsistent databases. Well ... I was hoping you would answer that there already is a mechanism in place that would help the clients to safely detect the inconsistent situation and force them to reconnect. Stephan -- 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.
