Re: Stick-table peers expiration time

Hi Igor, On Fri, Feb 19, 2016 at 06:48:13PM +1100, Igor Cicimov wrote: > Hi Willy, > > On 04/02/2016 3:11 PM, "Willy Tarreau" wrote: > > > > On Wed, Feb 03, 2016 at 11:05:03AM +1100, Igor Cicimov wrote: > > > Any comments on this? Shouldn't the expiration time get replicated upon >

Re: Stick-table peers expiration time

Hi Willy, On 04/02/2016 3:11 PM, "Willy Tarreau" wrote: > > On Wed, Feb 03, 2016 at 11:05:03AM +1100, Igor Cicimov wrote: > > Any comments on this? Shouldn't the expiration time get replicated upon > > restart or just the keys? Obviously the entry in the first server stick > > table

Re: Stick-table peers expiration time

On Wed, Feb 03, 2016 at 11:05:03AM +1100, Igor Cicimov wrote: > Any comments on this? Shouldn't the expiration time get replicated upon > restart or just the keys? Obviously the entry in the first server stick > table will expire much sooner than the one on the restarted server meaning > the first

Re: Stick-table peers expiration time

Any comments on this? Shouldn't the expiration time get replicated upon restart or just the keys? Obviously the entry in the first server stick table will expire much sooner than the one on the restarted server meaning the first one might choose different backend for the same session id. Thanks,

Stick-table peers expiration time

Hi all, I have the following entry in a stick-table: 0x87bf54: key=09643F891F0C6F7BE467E619952E327E use=0 exp=1938168 server_id=1 and on the peer after doing a restart: 0x806934: key=09643F891F0C6F7BE467E619952E327E use=0 exp=4795722 server_id=1 can see the same entry with different