mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-22 14:21:25 +02:00
9e647e5af7
When the processing stage is finished for a SPOE applet, before returning it into the idle list, we check if the assigned server appears as full or if there are some pending connections on the backend or the assigned server. If yes, it means we reach a maxconn and we close the applet to free a slot. Otherwise, the applet can be reused. This test is only performed if there are more than one thread. It is important to close SPOE applets when there are pending connections for multithreaded instances because connections with the SPOE agents are persistent and local to a thread (applets are local to a thread). If a maxconn is configured, some threads may take all available slots for a while, leaving remaining threads without any free slot to process SPOE messages. It is especially true if the maxconn is low. This patch should fix the issue #705. It must be backported as far as 1.8. However, the code in 1.8 is quite different, a test must be performed to be sure it works well.
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)