[Pacemaker] Best practice for quorum nodes

Andrey Groshev greenx at yandex.ru
Fri Apr 25 14:52:20 EDT 2014

Hi, Andrew.
Not sure what my version better, but I did so ..
In short, I use conventional configuration of the cluster postgresql.
Mainly in the resource hierarchy is a clone of the primitive "ping".
I add next line to reles:
location checkquorumnode clnPingCheck \
        rule $id="checkquorumnode-rule" -inf: not_defined thisquorumnode or thisquorumnode eq yes
Symmetric cluster. But resources are not run if this attribute is not defined.

18.04.2014, 18:46, "Andrew Martin" <amartin at xes-inc.com>:
> 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?
> 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