On Thu, May 20, 2010 at 9:55 AM, Mark Huijgen <[email protected]> wrote: > > On 05/20/2010 03:37 PM, Derrick Brashear wrote: >>> So thats 3 keepalives to server afs3 every 20 seconds where it started >>> off with just 1 every 20 seconds. >>> Is this expected behaviour that it keeps sending more and more packets >>> to the same fileserver? >>> >> How many authentication contexts do you have? >> > Only 1 afs account/token is used on the client since it started.
So 2: noauth and the token. > >>> The number of entries returned by running 'rxdebug localhost 7001 >>> -allconnections' on the client seems to grow with the number of packets >>> sent every 20s to each server (see attachment, ip's replaced with short >>> hostnames to match tcpdump output). >>> >>> vlserver pings do seem to stop when the connection to the vlserver is >>> destroyed, just not the fileserver ones. >>> >> Connections to the fileserver get replaced. It's an artifact of how >> the cache manager tracks servers. >> > > Does replace mean the old connection will(should?) be destroyed together > with the scheduled natping for it? An old connection is destroyed only when a new one is created. Again, one per auth context. You can't use a destroyed connection for a nat ping, for obvious reasons. I could tune this slightly. -- Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
