[Pacemaker] monitor on disabled nodes

[Andrew Beekhof]

On 19/09/2013, at 2:13 AM, Radoslaw Garbacz <radoslaw.garbacz at xtremedatainc.com> wrote:

> Hi,
> 
> I have a question regarding the "monitor" operation on disabled nodes.
> 
> I noticed that this operation is called even, when an agent is disabled for a node. Is it an indented behavior

Yes.  We have to check the resource's status on that node to make sure it isn't already running there.

> or is there something wrong with my configuration?
> 
> Another question is, if it is intended, whether there is any way to distinguish such a call from a normal health check of a running agent (like "ocf_is_probe" for "validate-all" operation)?

Be careful not to unconditionally return 'stopped' for probes.  There are plenty of situations where we could probe for a resource with the expectation that it _is_ running.

> 
> 
> Thanks in advance,
> 
> 
> -- 
> Best Regards,
> 
> Radoslaw Garbacz
> XtremeData Incorporation
> _______________________________________________
> 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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130919/453f6446/attachment-0004.sig>