[Pacemaker] Prevent resources from even being checked on one node

Andrew Beekhof andrew at beekhof.net
Thu Apr 26 21:58:18 EDT 2012

On Mon, Apr 23, 2012 at 8:16 PM, Lars Marowsky-Bree <lmb at suse.com> wrote:
> On 2012-04-21T10:15:23, Arnold Krille <arnold at arnoldarts.de> wrote:
>> But I still get error-messages ($OCF_ERR_NOT_INSTALLED) when the cluster tries
>> to monitor the resources on the third node. I don't want that. I want the
>> cluster to either not even run monitor (for these resources) on the third node
>> or to ignore monitor-errors from these resources on the third node.
>> How to achieve this? Do I have to add anti-location rules for all the
>> resources in that group individually?
> No. The cluster will always run the probes to find out if the service is
> active there by accident.

Or still running there after a crash.  Or after someone ran "crm
resource cleanup".

> You cannot disable this safely.
> Regards,
>    Lars
> --
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
> _______________________________________________
> 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

More information about the Pacemaker mailing list