Hi, > Say, the DB runs on nodes A and B. They are accessed from node C.
> As I understand, H2 clustering is achieved by C connecting to A and to B. Yes. > What happens if network connectivity is lost between A and C (with B still running)? > Am I right that C will see only B and assume that the cluster is running only on one 'leg' ? Yes. > This would mean that when network connectivity comes up again there is no reason for C to reconnect to A .... simply because there is no event to trigger such a reconnect. That's true. > As far as I understand, a rebuild of the cluster would cause a disconnect for C, which then reconnects to A and B. However, A and B are still running quite perfect (still serving other clients) ... so there is no reason to rebuild the cluster. 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." At least that's how it should work. I have to admit there is a lot of room how this could be improved. 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.
