On Wednesday 09 April 2008 16:53:41 Dejan Muhamedagic wrote: > Hi, > > On Tue, Apr 08, 2008 at 08:18:14PM +0200, Bernd Schubert wrote: > > On Tuesday 08 April 2008 19:32:58 Bernd Schubert wrote: > > > Hello, > > > > > > I need to set a rather huge dead time of 1200s, but the initial dead > > > time is supposed to be of 120s or less. However, heartbeat tries to be > > > schoolmasterly and doesn't want to accept my settings: > > > > > > deadtime 1200 # time to declare a node dead > > > initdead 120 # time to declare a node dead on heartbeat startup > > > keepalive 120 # how often to send keepalive packets > > > > > > > > > heartbeat[6523]: 2008/04/08_19:23:16 ERROR: Initial dead time [120000] > > > is smaller than deadtime [1200000] > > > eartbeat[6523]: 2008/04/08_19:23:16 ERROR: Configuration error, > > > heartbeat not started. > > > > > > > > > Well, heartbeat is not startup up automatically here and even the nodes > > > are not powered on automatically after a hard reset. So when I start > > > heartbeat I'm activeley monitoring everything and there is absolutely > > > no need to let me wait at least 20min on start up. I'm even not > > > convinced a deadtime of 20min is sufficient, since this is for a Lustre > > > cluster and Lustre sometimes manages to create such a high load that > > > nothing else than the Lustre and related kernel threads do work on the > > > system... > > > > > > So pretty please, is there a setting allowing to override this > > > ridiculous initdead time checking? > > This looks like a valid use case. The patch to issue just a > warning instead of stopping with a configuration error you can > find here: > > http://hg.linux-ha.org/dev/rev/01ef2fcb540e
Thanks, this looks fine. I'm going to apply it to our version. > > Note that you'd have to adjust all timeouts to something larger > than the deadtime. It's reasonable to assume that everything else > is going to be delayed even more than heartbeats. Yes, all other heartbeat timeouts are already huge. Thanks for your help, Bernd -- Bernd Schubert Q-Leap Networks GmbH _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
