mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 22:01:31 +02:00
fe29dba872
When entering closing state, a QUIC connection is maintained during a certain delay. The principle is to ensure the other peer has received the CONNECTION_CLOSE frame. In case of packet duplication/reordering, CONNECTION_CLOSE is reemitted. QUIC RFC recommends to use at least 3 times the PTO value. However, prior to this patch, haproxy used instead the max value between 3 times the PTO and the connection idle timeout. In the default case, idle timeout is set to 30s which is in most of the times largely superior to the PTO. This has the downside of keeping the connection in memory for too long whereas all resources could be released much earlier. Fix this behavior by using 3 times the PTO on closing or draining state. This value is limited up to 1s. This ensures that most of connections are covered by this. If a connection runs with a very high RTT, it must not impact the whole process and should be released in a reasonable delay. This should be backported up to 2.6.
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)