On 23/07/2013, at 11:28 AM, Tan Tai hock <taih...@gmail.com> wrote: > Hi, > > I have currently set up 3 machines with Pacemaker 2.3 with Corosync 1.19. I > have tested some scenarios and have encountered some problem which I hope to > get some advice on. > > My scenario is as follows: > > The 3 machines, name A,B,C are all running with A being the node which > started the resource as seen in cm_mon. If I were to cut off the network > connection for A, B will take over as the node which started the resource. I > then resume the network connection and start both corosync and pacemaker on A > again
Did you stop it there first? > and the node which started the resource now returns to node A. > I have set stickness and perform an identical test but with proper shutdown > of pacemaker and corosync and it is working fine. > Is there anyway to perform a clean shutdown in the event that a node loses > network connection so that it will not attempt to take back the resource it > used to be holding before it was uncleanly shutdown? > > Thanks > _______________________________________________ > 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://bugs.clusterlabs.org _______________________________________________ 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://bugs.clusterlabs.org
