[Pacemaker] don't want to restart clone resource

[Fanghao Sha]

Hi Andrew,
Is crm_report included in pacemaker-1.0.12-1.el5.centos?
I couldn't find it.

2012/2/4 Andrew Beekhof <andrew at beekhof.net>

> On Fri, Feb 3, 2012 at 9:35 PM, Fanghao Sha <shafanghao at gmail.com> wrote:
> > Sorry, I don't know how to file a bug,
>
> See the links at the bottom of every mail on this list?
>
> > and i have only "messages" file.
>
> man crm_report
>
> >
> > I have tried to set clone-max=3, and after removing node-1, the clone
> > resource running on node-2 has not restart.
> > But when I add another node-3 to cluster with "hb_addnode", the clone
> > resource running on node-2 became orphaned and restart.
> >
> > As attached "messages" file,
> > I couldn't understand this line:
> > "find_clone: Internally renamed node-app-rsc:2 on node-2 to
> node-app-rsc:3
> > (ORPHAN)".
> >
> > 2012/2/2 Andrew Beekhof <andrew at beekhof.net>
> >>
> >> On Thu, Feb 2, 2012 at 4:57 AM, Lars Ellenberg
> >> <lars.ellenberg at linbit.com> wrote:
> >> > On Wed, Feb 01, 2012 at 03:43:55PM +0100, Andreas Kurz wrote:
> >> >> Hello,
> >> >>
> >> >> On 02/01/2012 10:39 AM, Fanghao Sha wrote:
> >> >> > Hi Lars,
> >> >> >
> >> >> > Yes, you are right. But how to prevent the "orphaned" resources
> from
> >> >> > stopping by default, please?
> >> >>
> >> >> crm configure property stop-orphan-resources=false
> >> >
> >> > Well, sure. But for "normal" ophans,
> >> > you actually want them to be stopped.
> >> >
> >> > No, pacemaker needs some additional smarts to recognize
> >> > that there actually are no orphans, maybe by first relabling,
> >> > and only then checking for instance label > clone-max.
> >>
> >> Instance label doesn't come into the equation.
> >> It might look like it does on the outside, but its more complicated than
> >> that.
> >>
> >> >
> >> > Did you file a bugzilla?
> >> > Has that made progress?
> >> >
> >> >
> >> > --
> >> > : Lars Ellenberg
> >> > : LINBIT | Your Way to High Availability
> >> > : DRBD/HA support and consulting http://www.linbit.com
> >> >
> >> > _______________________________________________
> >> > 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
> >>
> >> _______________________________________________
> >> 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
> >
> >
> >
> > _______________________________________________
> > 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
> >
>
> _______________________________________________
> 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/20120208/050095c4/attachment-0003.html>