I have a pgsql resource set up on my 2-node heartbeat 2.1.3 cluster in
CRM. I'd like to be able to restart Postgres when I made configuration
changes, but I've found that if the database is busy (thus making the
Postges restart take some time) the nodes can fail over because
Heartbeat thinks that Postgres has died.
I could lengthen the monitor and deadtime intervals, but I like how
responsive it is to a real problem right now, so is there any easy, or
at least possible, way that I can tell heartbeat to take a resource down
and start it up again on the same node? Nothing depends upon Postgres
in the ordering constraints, so I won't have to worry about it taking
other resources with it, but I would very much like to be able to
restart without failing over.
--
Adrian Overbury
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
