Not sure if this is a "problem" per se, but I'm here's my situation:
I have a cluster set up with CentOS + Heartbeat v1 + DRBD + NFSv4. When I failover from one node to the other (by stopping the heartbeat service on the primary node), I get these messages in /var/log/messages after starting the NFS service on the secondary: kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory kernel: NFSD: starting 90-second grace period The web sites that have to access the NFS drive are then unavailable for about 90 seconds. After that, then everything works. My question is: is there any way to get rid of this 90-second grace period when NFSv4 starts up? Other info: The /var/lib/nfs/ directory is shared between nodes: each node has a symlink to the nfs directory on the DRBD device. I've added the "killproc nfsd -9" line to the /etc/init.d/nfs startup script My /etc/ha.d/haresources file: my.primary.node IPaddr::192.168.0.251/24 drbddisk::data Filesystem::/dev/drbd0::/data::ext3::defaults mysql nfs My /etc/ha.d/ha.cf file: keepalive 1 deadtime 10 warntime 5 initdead 120 udpport 694 bcast eth1 auto_failback off node my.primary.node node my.secondary.node _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
