mirror of
https://github.com/haproxy/haproxy.git
synced 2026-03-12 21:52:52 -04:00
HAProxy - Load balancer
f822decfda
When a connection attempt failed, if a retry is possible, the SI endpoint on the server side is immediately released, instead of waiting to establish a new connection to a server. Thus, when the backend SI is switched from SI_ST_CER state to SI_ST_REQ, SI_ST_ASS or SI_ST_TAR, its endpoint is released. It is expected because the SI is moved to a state prior to the connection stage ( < SI_ST_CONN). So it seems logical to not have any server connection. It is especially important if the retry is delayed (SI_ST_TAR or SI_ST_QUE). Because, if the server connection is preserved, any error at the connection level is unexpectedly relayed to the stream, via the stream-interface, leading to an infinite loop in process_stream(). if SI_FL_ERR flag is set on the backend SI in another state than SI_ST_CLO, an internal goto is performed to resync the stream-interfaces. In addtition, some ressources are not released ASAP. This bug is quite old and was reported 1 or 2 times per years since the 2.2 (at least) with not enough information to catch it. It must be backported as far as 2.2 with a special care because this part has moved several times and after some observation period and feedback from users to be sure. For info, in 2.0 and prior, the connection is released when an error is encountered in SI_ST_CON or SI_ST_RDY states. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)