>From the old linux-ha.org/HaNFS page, Hint #2:
If your kernel defaults to using TCP for NFS (as is the case in 2.6
kernels), switch to UDP instead by using the 'udp' mount option. If
you don't do this, you won't be able to quickly switch from server
"A" to "B" and back to "A" because "A" will hold the TCP connection
in TIME_WAIT state for 15-20 minutes and refuse to reconnect.
Are you mounting with TCP? A minute sounds short.
- Dave
On Fri, Feb 04, 2011 at 10:45:22AM +0000, Ricardo Botelho de Sousa wrote:
> Hello All!
>
> We have implemented a solution based around heartbeat v3 and DRBD.
> While everything seems to work very well we have some difficulty with
> regard to the time it takes for the NFS service to become fully available.
>
> How long it is expected for a graceful fail-over with NFSv4 to take?
> We tried reducing grace/lease times to no avail. We don't seem to be
> able to lower it from about a minute. TCP or UDP doesn't seem to make
> any difference.
>
> It's not that I believe this is related to Heartbeat, but perhaps find
> an explanation or some mysterious parameter from your collective experience.
>
> Best regards,
>
> --
> ServiSMART Ricardo Sousa
> servimos o seu neg?cio tel: +351 96 298 0989
>
> _______________________________________________
> 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
