[OpenAFS] [1.2.7] Strange file server meltdown

[Nathan Neulinger]

This is interesting... I drop RXDEADTIME to 10, and set
DEFAULT_PROBE_INTERVAL to 60, but have never messed with HARDDEADTIME.

What's the difference between the hard and soft timeouts?

-- Nathan

> The problem is that the server keeps responding to the Rx pings, so the
> client doesn't think the server is down, just slow.  And the Unix clients
> don't set a hard dead timeout by default, so it keeps trying forever.  On
> my own client builds, I use this change that makes things time out much
> faster:
> 
> --- afs.h	2002/10/16 03:58:15	1.35
> +++ afs.h	2002/12/13 04:42:18
> @@ -83,8 +83,8 @@
>  #define	AFS_LRALLOCSIZ 	4096	    /* "Large" allocated size */
>  #define	VCACHE_FREE	5
>  #define	AFS_NRXPACKETS	80
> -#define	AFS_RXDEADTIME	50
> -#define AFS_HARDDEADTIME        120
> +#define	AFS_RXDEADTIME	10
> +#define AFS_HARDDEADTIME 30
>  
>  struct sysname_info {
>    char *name;
> 
> --- afs_conn.c	2002/10/16 03:58:16	1.10
> +++ afs_conn.c	2002/12/13 04:42:18
> @@ -226,9 +226,7 @@
>  	AFS_GUNLOCK();
>  	tc->id = rx_NewConnection(sap->sa_ip, aport, service, csec, isec);
>  	AFS_GLOCK();
> -        if (service == 52) { 
> -           rx_SetConnHardDeadTime(tc->id, AFS_HARDDEADTIME);
> -       }
> +        rx_SetConnHardDeadTime(tc->id, AFS_HARDDEADTIME);
>  
> 
>  	tc->forceConnectFS = 0;	/* apparently we're appropriately connected now */
> 
> -- kolya
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
-- 

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216