[Pacemaker] Corosync resources actions when a node (re)joins

[Andrew Beekhof]

On Tue, Mar 29, 2011 at 5:39 PM, Stephan-Frank Henry
<Frank.Henry at gmx.net> wrote:
> Hello again,
>
> I was doing some tests with some LSB resources and noticed that when one of the nodes is removed (corosync stop) and then rejoins (start), regardless of who is currently master and who is slave, the LSB resource will fire a [stop] and then a [start].

I'm guessing the script isnt LSB compliant.
Have you tested it against:
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html

>
> As I am trying to control a resource that takes some time to deploy and resume operations again, this is not really desireable.
>
> My question is, what controls this behavior?
>
> thanks
>
> bye
> --
> NEU: FreePhone - kostenlos mobil telefonieren und surfen!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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
>