I've found with stick tables the expiry time is only reset when you have a connection attempt that hits the same stick table entry: Traffic has no bearing. You can use socat on the stats socket to show the expiry time of a socket entry.
But traffic does have bearing on the client/server/tunnel timeout commands - be that in the default, frontend or backend config. I've not figured out a way to see the current client/server/tunnel timeout value - but have tested this behaviour. We use stick tables to keep long polling on the same back-end server for sessions that cannot elevate to a websocket. Cheers, Brian On 19 December 2016 at 07:01, Willy Tarreau <[email protected]> wrote: > Hi Dennis, > > On Thu, Dec 15, 2016 at 01:20:19PM +0100, Dennis Jacobfeuerborn wrote: > > Hi, > > I'm wondering how i can keep long running tcp sessions in the stick > > table. It seems that when I use mode tcp and a stick table then an entry > > gets initially created when a connection is established but even though > > traffic is flowing back and forth for that connection the entry > > eventually expires and never gets refreshed. > > Is there a way to refresh the entry as long as traffic is flowing and > > only let it expire when no traffic has been seen for X minutes? > > When you use track-sc, a reference is taken to the entry in the table > and it (normally) cannot expire. How do you use the stick table in your > case ? Do you have an example config that shows the problem ? I'm just > trying to find if that's just a config issue, a bug or a design limitation. > > Cheers, > Willy > >
