[ClusterLabs] When resource fails to start it stops an apparently unrelated resource

[Gerard Garcia]

Thanks Ken. Yes, inspecting the logs seems that the failcount of the
correctly running resource reaches the maximum number of allowed failures
and gets banned in all nodes.

What is weird is that I just see how the failcount for the first resource
gets updated, is like the failcount are being mixed. In fact, when the two
resources get banned the only way I have to make the first one start is to
disable the failing one and clean the failcount of the two resources (it is
not enough to only clean the failcount of the first resource) does it make
sense?

Gerard

On Mon, Oct 16, 2017 at 6:57 PM, Ken Gaillot <kgaillot at redhat.com> wrote:

> On Mon, 2017-10-16 at 18:30 +0200, Gerard Garcia wrote:
> > Hi,
> >
> > I have a cluster with two ocf:heartbeat:anything resources each one
> > running as a clone in all nodes of the cluster. For some reason when
> > one of them fails to start the other one stops. There is not any
> > constrain configured or any kind of relation between them.
> >
> > Is it possible that there is some kind of implicit relation that I'm
> > not aware of (for example because they are the same type?)
> >
> > Thanks,
> >
> > Gerard
>
> There is no implicit relation on the Pacemaker side. However if the
> agent returns "failed" for both resources when either one fails, you
> could see something like that. I'd look at the logs on the DC and see
> why it decided to restart the second resource.
> --
> Ken Gaillot <kgaillot at redhat.com>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> 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/users/attachments/20171017/2b6c1353/attachment-0003.html>