f521c2ce2d
When a server is deleted via "del server", increment refcount of its parent backend. This is necessary as the server is not referenced anymore in the backend, but can still access it via its own <proxy> member. Thus, backend removal must not happen until the complete purge of the server. The proxy refcount is released in srv_drop() if the flag SRV_F_DELETED is set, which indicates that "del server" was used. This operation is performed after the complete release of the server instance to ensure no access will be performed on the proxy via itself. The refcount must not be decremented if a server is freed without "del server" invokation. Another solution could be for servers to always increment the refcount. However, for now in haproxy refcount usage is limited, so the current approach is preferred. It should also ensure that if the refcount is still incremented, it may indicate that some servers are not completely purged themselves. Note that this patch may cause issues if "del backend" are used in parallel with LUA scripts referencing servers. Currently, any servers referenced by LUA must be released by its garbage collector to ensure it can be finally freed. However, it appeas that in some case the gc does not run for several minutes. At least this has been observed with Lua version 5.4.8. In the end, this will result in indefinitely blocking of "del backend" commands. |
||
|---|---|---|
| .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.