Hi, On Mon, Sep 21, 2009 at 11:15:51AM +0200, Andrew Beekhof wrote: > On Fri, Sep 18, 2009 at 12:52 PM, Enno Gröper > <[email protected]> wrote: > > Hi, > > I'm using pacemaker with heartbeat to run a 2 node dhcp server cluster > > with shared disk using drbd for the lease file. > > After upgrading from using heartbeat 2.1.3 (lenny packages) alone (I > > purged the old install and removed rest of the old files by hand) I have > > some strange problems. > > When stopping the monitored dhcp service using "/etc/init.d/dhcp3-server > > stop" pacemaker recognises this as expected, but instead of simply > > trying to restart the resource on the same node it leaves it stopped > > (the other node is in standby mode). > > To achieve what I want (and what I think was default behaviour using > > heartbeat 2.1.3) I set migration_threshold to 1. > > However failcount is set to INFINITY instead of being increased by 1 so > > this doesn't matter. > > I thougt failcount is only set to INFINITY if failures occur on starting > > a resource? > > With migration-threshold = 1, _any_ failure will force the resource to > another node. > Including monitor failures.
And if the other node is in standby then the resource remains down. I still find that counterintuitive. To put it differently: How to configure pacemaker to always do a failover to another node, but to restart the resource in case other nodes are not available. Thanks, Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
