[Pacemaker] Stop vs orphan stop using notify

Yogesh Patil yogeshpatil111 at gmail.com
Wed Jan 29 11:12:52 EST 2014

I am creating a clone of a group. Although clone-max is 2, it creates
resources on all nodes in the cluster and then convert all but 2 to orphan
stop state(crm_mon output). I want to ommit such state but all I get is
stopped resource.

On 29-Jan-2014 5:08 pm, "Lars Marowsky-Bree" <lmb at suse.com> wrote:

> On 2014-01-29T14:00:38, Yogesh Patil <yogeshpatil111 at gmail.com> wrote:
> > I am doing some destructive actions on stopped state. But I don't want to
> > do them it is ORPHAN stop. How can I differentiate in CRM_notify_* values
> > coming from environment variables.
> What do you mean by "orphan stop"?
> And how do your services end up in this state?
> Regards,
>     Lars
> --
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix
> Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
> _______________________________________________
> 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 --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140129/5bc9bf45/attachment-0003.html>

More information about the Pacemaker mailing list