[DRBD-user] degr-wfc-timeout ignored

Lars Ellenberg lars.ellenberg at linbit.com
Fri Sep 7 20:07:01 CEST 2007

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Fri, Sep 07, 2007 at 10:22:36AM -0000, Karl Pálsson wrote:
> Hi,
> I have degr-wfc-timeout set to 60. The cluster is degraded (the
> secondary is offline). Then I reboot the Primary and it waits forever
> for the Secondary! Is it not supposed to give up after 60 seconds?

as currently implemented,
the degr-wfc-timeout is _only_ used when
recovering from a degraded crash.

 Primary, no Secondary, crash
 automatic reboot
 detect that I had been degraded Primary,
 so I use the degr-wfc-timeout.

why not for a clean reboot of a standalone Primary?

 first, because _every_ clean reboot looks the same way:
 become secondary, disconnect, unconfigure, reboot.
 so we have been "disconnected" (degraded?) before the reboot.

 second, because if you do a clean reboot,
 aparently you are at the box anyways,
 so you can interactively interrupt the "wait-forever".

: Lars Ellenberg                            Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :
please use the "List-Reply" function of your email client.

More information about the drbd-user mailing list