On Tue, Sep 20, 2011 at 01:45:43PM +0200, RaSca wrote:
> Il giorno Mar 20 Set 2011 12:53:40 CEST, Dejan Muhamedagic ha scritto:
> [...]
> > on-fail is a per-operation attribute. By default, it is set to
> > fence only for the stop operation. The point is that a failed
> > stop means that the cluster cannot establish the state of the
> > resource anymore, so the only remedy remaining is to fence the
> > node.
> > Thanks,
> > Dejan
> 
> And I completely agree with this, but in an environment like mine, where 
> a single resource failure might involve all the others (with fence) is 
> wronk to keep this kind of settings. Do you agree with me?

No. If the resource cannot stop, then something's wrong either
with the resource or with the RA. And needs to be fixed.

> It has more sense to have the resource stopped or unmanaged instead of 
> doing a node fence.
> So, even if I had to patch the Virtualdomain RA with Micheal's one 
> (http://www.gossamer-threads.com/lists/linuxha/dev/74103) it may be 
> useful for me to set the stop operations on-fail parameter to "stop", or 
> maybe "block", like this:
> 
> op monitor interval="10" timeout="30" start-delay="0" on-fail="stop"
> 
> Am I right?

If a resource fails to stop, then on-fail="stop" cannot possibly
help. Furthermore, you basically make this resource less
available (the cluster won't try to recover it). Must be that
I'm missing something.

At any rate, I don't think that you need to fiddle with the
on-fail attribute, but see what's wrong with the RA or libvirt
or the combination of the two.

Thanks,

Dejan

> -- 
> RaSca
> Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene!
> [email protected]
> http://www.miamammausalinux.org
> 
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to