On 2013-07-08 19:40, Jeff Frost wrote: > We're testing out the pgsql master slave streaming replication resource agent > that's found here: > > https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/pgsql > > and using the example 2-node configuration found here > https://github.com/t-matsuo/resource-agents/wiki/Resource-Agent-for-PostgreSQL-9.1-streaming-replication > as a template, we came up with the following configuration: > > > node node1 > node node2 > primitive pgsql ocf:heartbeat:pgsql \ > params pgctl="/usr/pgsql-9.2/bin/pg_ctl" psql="/usr/pgsql-9.2/bin/psql" > pgdata="/var/lib/pgsql/9.2/data/" start_opt="-p 5432" rep_mode="async" > node_list="node1 node2" repuser="replicauser" restore_command="rsync -aq > /var/lib/pgsql/wal_archive/%f %p" master_ip="192.168.253.104" > stop_escalate="0" \ > op start interval="0s" role="Master" timeout="60s" on-fail="block"
Looks like you are missing the monitor operations ... as described in the example you are referring. In the monitoring operation such master-slave agents recalculate their master-score and refresh e.g. in this RA various node-attributes. And you should follow the described procedures to correctly start-up the cluster. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
