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="checkquoru
- Original Message -
> From: "David Vossel"
> To: "The Pacemaker cluster resource manager"
> Sent: Monday, April 21, 2014 10:39:22 AM
> Subject: Re: [Pacemaker] Best practice for quorum nodes
> > Is there a better way to designate a node as a quorum
- Original Message -
> From: "Andrew Martin"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, April 18, 2014 9:38:45 AM
> Subject: [Pacemaker] Best practice for quorum nodes
>
> Hello,
>
> I've read several guides
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
