Hi, On Mon, Jan 11, 2010 at 03:21:05PM -0500, David Sickmiller wrote: > Hi, > > > > I was hoping to configure my 2-node cluster to start as soon as both > nodes were present but wait up to 15 minutes if the other node was > missing upon system startup. In my case, a delay of several minutes is > better than a split-brain scenario. The Linux-HA documentation says > "The initdead parameter is used to set the time that it takes to declare > a cluster node dead when Heartbeat is first started.", so I figured I > could just set "initdead 900" in ha.cf. Unfortunately, heartbeat seems > to be waiting for the entire initdead time interval regardless of > whether all the nodes are present. > > > > Does this match others' experiences? Is there a different setting that > could accomplish my objective? > > > > It seems like the documentation would be more accurate if it said "The > initdead parameter is used to set the time that heartbeat waits before > starting any resources, which allows time for additional nodes to join."
If you have autojoin set to "any". > However, I would much prefer that Linux-HA behaved according to the > original documentation. > > > > I'm using Heartbeat 2.1.4 on RHEL 5.4. Please switch to Pacemaker/heartbeat or Pacemaker/corosync. Or are you using v1/haresources? Thanks, Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
