[Pacemaker] Best practice for quorum nodes

David Vossel dvossel at redhat.com
Mon Apr 21 11:39:22 EDT 2014

----- Original Message -----
> From: "Andrew Martin" <amartin at xes-inc.com>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Friday, April 18, 2014 9:38:45 AM
> Subject: [Pacemaker] Best practice for quorum nodes
> Hello,
> I've read several guides about how to configure a 3-node cluster with one
> node that can't actually run the resources, but just serves as a quorum
> node. One practice for configuring this node is to put it in "standby",
> which prevents it from running resources. In my experience, this seems to
> work pretty well, however from time-to-time I see these errors appear in my
> pacemaker logs:
> Preventing <rsc> from re-starting on <host>: operation monitor failed 'not
> installed' (rc=5)
> Is there a better way to designate a node as a quorum node, so that resources
> do not attempt to start or re-start on it? Perhaps a combination of setting
> it in "standby" mode and a resource constraint to prevent the resources from
> running on it? Or, is there a better way to set it up?

Pacemaker is going to probe the node for active resources regardless. If you don't want to see these errors, make sure the resource-agents and resource-agent dependent packages are installed on all nodes in the cluster.

-- Vossel

> Thanks,
> Andrew
> _______________________________________________
> 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