sinjuginas/haproxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DOC: peers: clarify when entry expiration date is renewed.

Browse Source 
This patch add some details to know which rules are updating
the expiration timer of an entry.

It also adds a comment to know how to fetch a value without renewing
this timer.

This patch addresses github issue #615

This patch should be backported on all still supported branches
This commit is contained in:
Emeric Brun 2022-05-30 18:08:28 +02:00 committed by Christopher Faulet
parent 0f4a02b81a
commit 423ed389ac
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/configuration.txt
View File

@ -11619,13 +11619,16 @@ stick-table type {ip | integer | string [len <length>] | binary [len <length>]}
soft restart.
<expire> defines the maximum duration of an entry in the table since it
was last created, refreshed or matched. The expiration delay is
was last created, refreshed using 'track-sc' or matched using
'stick match' or 'stick on' rule. The expiration delay is
defined using the standard time format, similarly as the various
timeouts. The maximum duration is slightly above 24 days. See
section 2.5 for more information. If this delay is not specified,
the session won't automatically expire, but older entries will
be removed once full. Be sure not to use the "nopurge" parameter
if not expiration delay is specified.
Note: 'table_*' converters performs lookups but won't update touch
expire since they don't require 'track-sc'.
<srvkey> specifies how each server is identified for the purposes of the
stick table. The valid values are "name" and "addr". If "name" is