On Wed, Apr 27, 2011 at 7:18 PM, Stallmann, Andreas <astallm...@conet.de> wrote: > Hi Andrew, > >> According to your configuration, it can be up to 60s before we'll detect a >> change in external connectivity. >> Thats plenty of time for the cluster to start resources. >> Maybe shortening the monitor interval will help you. > > TNX for the suggestion, I'll try that. Any suggestions on recommended monitor > intervals for pingd? > >> Couldn't hurt. > Hm... if I - for example, set the monitor interval to 10s, I'd have to adjust > the timeout for monitor to 10s as well, right?
Right. > Ping is quite sluggish, it takes up to 30s to check the three nodes. Sounds like something is misconfigured. > If I now adust the interval to 10s, the next check might be triggered before > the last one is complete. Will this confuse pacemaker? No. The next op will happen 10s after the last finishes. > >>> Yes, and there is no proper way to use DRBD in a three node cluster. >> How is one related to the other? >> No-one said the third node had to run anything. > > Ok, thanks for the info; I thought all members of the cluster had to be able > to run cluster resources. I would have to keep resources from trying to run > on the third node then via a location constrain, right? Or node standby. > > TNX for your input! > > Andreas > > ------------------------ > CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. > Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) > Geschäftsführer/Managing Directors: Jürgen Zender (Sprecher/Chairman), Anke > Höfer > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
