Hi On Wed, 16 Jul 2008, "David Coulson" <[EMAIL PROTECTED]> wrote: > The stickyness works fine on the local server, however when it syncs > over to the backup, the timeout is wrong. > > On master: > TCP 29:53 NONE 103.90.0.17:0 103.200.100.1:80 103.75.25.76:80 > > On slave: > TCP 02:57 NONE 103.90.0.17:0 103.200.100.1:80 103.75.25.76:80
Hrm... this is due to the synchronised connections being given a 3 minute timeout on the the backup so that backup director doesn't end up stuffed full of closed connections. Incidentally, a patch has just been accepted to make the synchronised connections go away on the backup when they go away on the master director (ie. when they reach CLOSE, CLOSE_WAIT or TIME_WAIT). But that won't solve this. > Obviously there are instances when the backup connections timeout but > they are in place on the master, so in the event the master fails, the > slave doesn't have the connections in it's table. With a non-open but persistent connection (say one which has been closed for 5 minutes but still has 25 minutes of persistence left) what do you see on the backup director? Anything? If I recall correctly, they'll reach 0 seconds remaining and then spring back to 3 minutes, but I could be wrong. Graeme _______________________________________________ LinuxVirtualServer.org mailing list - [email protected] Send requests to [EMAIL PROTECTED] or go to http://lists.graemef.net/mailman/listinfo/lvs-users
