b8961ee8b3
avail_streams callback serves to indicates how many streams can be attached for a backend connection. On QUIC mux, this relies on several parameters, first based on static limitation which only decreases over time, but also on flow control which is dynamically adjusted by the peer and can be increased or decreased at will. qcc_is_dead() on the other hand serves to determine if a connection can be removed. First, it must be inactive (no request in progress). Then, if a backend connection cannot be reused due to some of the above limitation reached, it is definitely useless and should be removed as soon as possible. However, prior to this patch, qcc_is_dead() did not take into account the same set of parameters than avail_streams : only if graceful shutdown was initiated by the peer was considered. The purpose of this patch is to linked these two functions together. Reuse calcul based on static limits is extracted from avail_streams() into new qcc_be_is_reusable(). This function is used directly in qcc_is_dead(), which now for example takes into account the server max-reuse parameter. This patch should ensure that a backend connection which can not be reuse anymore is release as soon as possible. This could improve slightly reuse rate in some specific scenarii as non-reusable connections should not pollute the idle cache. Return value of QUIC avail_streams() is changed by this patch as server max-reuse and max stream ID limits are now only taken into account when already exceeded or if a single stream remains. However, this has no consequence as callers of avail_streams() do not differentiates return value of 2 or more. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.