mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-19 00:51:37 +01:00
6e0afb2e27
To be able to delete a server, a number of preconditions must be validated to ensure it is not in used anymore. Previously, if idle connections were stored in the server, the deletion was cancelled. No action was implemented to force idle connection closure, the only solution was to wait for the periodic purging to be achieved. This is an extra burden to be able to delete a server. Indeed, idle connections are by definition inactive and can be closed prior to delete a server. This is the exact purpose of this patch. Idle connections removal is implemented inside "delete server" handler, once it has been determined that the server can be freely removed. A simple loop is run to call conn_release() over each idle connections. Takeover is also executed before conn_release() to ensure tasks/tasklets or any other sensible elements are not deleted from a foreign thread. This patch should reduce the occurence of rejected "delete server" execution, especially when connection reuse is high.
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)