[Pacemaker] prevent starting resources on failed node

Andrew Beekhof andrew at beekhof.net
Tue Jan 7 21:28:02 EST 2014

On 7 Dec 2013, at 2:17 am, Brian J. Murrell (brian) <brian at interlinx.bc.ca> wrote:

> [ Hopefully this doesn't cause a duplicate post but my first attempt
> returned an error. ]
> Using pacemaker 1.1.10 (but I think this issue is more general than that
> release), I want to enforce a policy that once a node fails, no
> resources can be started/run on it until the user permits it.

Node fails? Or resource on a node fails?
If you really mean "the node", just don't configure it to start pacemaker when it boots.

> I have been successful in achieving this using resource stickiness.
> Mostly.  It seems that once the resource has been successfully started
> on another node, it stays put, even once the failed node comes back up.
> So this is all good.
> Where it does seem to be falling down though is that if the failed node
> comes back up before the resource can be successfully started on another
> node, pacemaker seems to include the just-failed-and-restarted node in
> the candidate list of nodes it tries to start the resource on.  So in
> this manner, it seems that resource stickiness only applies once the
> resource has been started (which is not surprising; it seems a
> reasonable behaviour).
> The question then is, anyone have any ideas on how to implement such a
> policy?  That is, once a node fails, no resources are allowed to start
> on it, even if it means not starting the resource (i.e. all other nodes
> are unable to start it for whatever reason)?  Simply not starting the
> node would be one way to achieve it, yes, but we cannot rely on the node
> not being started.
> It seems perhaps the installation of a constraint when a node is
> stonithed might do the trick, but the question is how to couple/trigger
> the installation of a constraint with a stonith action?
> Or is there a better/different way to achieve this?
> Cheers,
> b.
> _______________________________________________
> 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://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140108/005ff280/attachment-0002.sig>

More information about the Pacemaker mailing list