I have a two node Pacemaker/Corosync cluster with no resources configured yet. I'm running RHEL 6.1 with the official 1.1.5-5.el6 package.
While doing various network configuration, I happened to notice that if I issue a "service network restart" on one node, then approx. four seconds later issue "service network restart" on the second node, the two nodes become split brain, each thinking the other is offline. Obviously, issuing 'service network restarts' four seconds apart will not be a common occurrence in production, but it concerns me that I can 'trick' the nodes into becoming split-brain so easily. Is there some way I can configure Corosync to quickly recover from this scenario? Alex _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
