RepoMirrors/haproxy
1
0
Fork 0
mirror of http://git.haproxy.org/git/haproxy.git/ synced 2025-04-18 04:55:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

[DOC] minor cleanup of the doc and notice to contributors

Browse Source
This commit is contained in:
Willy Tarreau 2008-01-22 12:25:31 +01:00
parent 5259dfedd1
commit 41a340d7c8
1 changed files with 33 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
doc/configuration.txt
View File

@ -4,13 +4,18 @@
---------------------- ----------------------
version 1.3.15 version 1.3.15
willy tarreau willy tarreau
2008/01/17 2008/01/22
This document covers the configuration language as implemented in the version This document covers the configuration language as implemented in the version
specified above. It does not provide any hint, example or advice. For such specified above. It does not provide any hint, example or advice. For such
documentation, please refer to the Reference Manual or the Architecture Manual. documentation, please refer to the Reference Manual or the Architecture Manual.
Note to documentation contributors : this document is formated with 80 columns
per line, with even number of spaces for indentation and without tabs. Please
follow these rules strictly so that it remains easily printable everywhere. If
a line needs to be printed verbatim and does not fit, please end each line with
a backslash ('\') and continue on next line.
HAProxy's configuration process involves 3 major sources of parameters : HAProxy's configuration process involves 3 major sources of parameters :
@ -3082,7 +3087,8 @@ timeout check <timeout>
"defaults" sections. This is in fact one of the easiest solutions not to "defaults" sections. This is in fact one of the easiest solutions not to
forget about it. forget about it.
See also: "timeout connect", "timeout queue", "timeout server", "timeout tarpit". See also: "timeout connect", "timeout queue", "timeout server",
"timeout tarpit".
timeout client <timeout> timeout client <timeout>
@ -3149,7 +3155,8 @@ timeout contimeout <timeout> (deprecated)
to use it to write new configurations. The form "timeout contimeout" is to use it to write new configurations. The form "timeout contimeout" is
provided only by backwards compatibility but its use is strongly discouraged. provided only by backwards compatibility but its use is strongly discouraged.
See also: "timeout check", "timeout queue", "timeout server", "timeout tarpit" "contimeout". See also: "timeout check", "timeout queue", "timeout server", "contimeout",
"timeout tarpit".
timeout http-request <timeout> timeout http-request <timeout>
@ -3777,19 +3784,28 @@ downinter <delay>
The "inter" parameter sets the interval between two consecutive health checks The "inter" parameter sets the interval between two consecutive health checks
to <delay> milliseconds. If left unspecified, the delay defaults to 2000 ms. to <delay> milliseconds. If left unspecified, the delay defaults to 2000 ms.
It is also possible to use "fastinter" and "downinter" to optimize delays It is also possible to use "fastinter" and "downinter" to optimize delays
between checks. When server state is: between checks depending on the server state :
- non-transitionally UP -> haproxy uses inter,
- transitionally UP (going down), unchecked or transitionally DOWN (going up) Server state | Interval used
-> haproxy uses "fastinter" if set or "inter" otherwise, ---------------------------------+-----------------------------------------
- down -> haproxy uses downinter if set or "inter" otherwise. UP 100% (non-transitional) | "inter"
Just as with every other time-based parameter, they can be entered in any other ---------------------------------+-----------------------------------------
explicit unit among { us, ms, s, m, h, d }. The "inter" parameter also serves Transitionally UP (going down), |
as a timeout for health checks sent to servers if "timeout check" is not set. Transitionally DOWN (going up), | "fastinter" if set, "inter" otherwise.
In order to reduce "resonance" effects when multiple servers are hosted on or yet unchecked. |
the same hardware, the health-checks of all servers are started with a small ---------------------------------+-----------------------------------------
time offset between them. It is also possible to add some random noise in the DOWN 100% (non-transitional) | "downinter" if set, "inter" otherwise.
health checks interval using the global "spread-checks" keyword. This makes ---------------------------------+-----------------------------------------
sense for instance when a lot of backends use the same servers.
Just as with every other time-based parameter, they can be entered in any
other explicit unit among { us, ms, s, m, h, d }. The "inter" parameter also
serves as a timeout for health checks sent to servers if "timeout check" is
not set. In order to reduce "resonance" effects when multiple servers are
hosted on the same hardware, the health-checks of all servers are started
with a small time offset between them. It is also possible to add some random
noise in the health checks interval using the global "spread-checks"
keyword. This makes sense for instance when a lot of backends use the same
servers.
maxconn <maxconn> maxconn <maxconn>
The "maxconn" parameter specifies the maximal number of concurrent The "maxconn" parameter specifies the maximal number of concurrent