On Wed, Dec 22, 2010 at 6:56 PM, Brad Johnson <[email protected]> wrote: > We are running heartbeat version 2.0.8. The scenario is when the active > device (device currently running our resource) is also the Designated > Controller. If that active device goes down there is an additional delay > of 40 seconds beyond the configured deadtime before the idle device > notices the DC has left the cluster. For example, our deadtime is set to > 30 seconds and it takes 70 seconds for the resource to fail-over. > If the active device is NOT the DC when it goes down, the fail-over > occurs after the expected deadtime of 30 seconds. > My question is: is there a way to force a particular node to become the > new DC?
No. Possibly you're hitting a bug in a hideously old version. > I tried 'crmadmin -E' but that doesn't change the DC. > > Here is our ha.cf: > > udpport 694 > keepalive 10 > deadtime 30 > warntime 23 > initdead 30 > bcast eth0.3999 > node ClariLink00123457 > auto_failback off > crm yes > autojoin any > ping x.x.x.x > ping y.y.y.y > respawn root /usr/lib/heartbeat/pingd -m 2000 -d 5s -a pld_ping_set > deadping 30 > use_logd yes > > Regards, > Brad > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
