[ClusterLabs] circumstances under which resources become unmanaged
ravikiran.n at hp.com
Thu Aug 13 00:27:06 EDT 2015
Thanks for reply Andrei. What happens to the resources added with a COLOCATION or an ORDER constraint with this resource (unmanaged FAILED resource).. ? will the constraint be removed.. ?
Also please point me to any resource to understand this in detail.
From: Andrei Borzenkov [mailto:arvidjaar at gmail.com]
Sent: Thursday, August 13, 2015 9:33 AM
To: Cluster Labs - All topics related to open-source clustering welcomed
Subject: Re: [ClusterLabs] circumstances under which resources become unmanaged
On 12.08.2015 20:46, N, Ravikiran wrote:
> Hi All,
> I have a resource added to pacemaker called 'cmsd' whose state is getting to 'unmanaged FAILED' state.
> Apart from manually changing the resource to unmanaged using "pcs resource unmanage cmsd" , I'm trying to understand under what all circumstances a resource can become unmanaged.. ?
> I have not set any value for "multilple-active" field, which means by default it is set to "stop-start", and hence I believe the resource can never go to unmanaged if it finds the resource active on more than one node.
unmanaged FAILED means pacemaker (or better resource agent) failed to stop resource. At this point resource state is undefined so pacemaker won't do anything with it.
> Also, it would be more helpful if anyone can point out to specific sections of the pacemaker manuals for the answer.
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org Getting started:
> Bugs: http://bugs.clusterlabs.org
Users mailing list: Users at clusterlabs.org http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
More information about the Users