Hi Andreas, * On Thu, Oct 30, 2008 at 02:16:21 +0100, Andreas Mock wrote:
> without knowing the reason why 10 seconds aren't enough to monitor drbd, > I do recommend to set the monitor timeout much higher. As the underlying DRBD device seemed to work properly during the monitoring timeouts, I set the time out value to 30 seconds with a check frequency of two minutes for evaluation. I might tighten those values later if this fixes the problem. > We had some discussions about proper action timeout values on this list. > The conclusion was: Better set it too long than too short. Why? When > timeout happens the cluster knows NOTHING. Can you really estimate > the worst interval for monitoring the ressource in a heavy load > scenario? [...] Thanks for your comments on this! Best regards, Jens -- /* www: http://blog.basquiat.de | gpg: 0x0E4D824B icq: 22849810 | jid: [EMAIL PROTECTED] */ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
