mirror of
https://github.com/haproxy/haproxy.git
synced 2026-04-15 21:59:41 -04:00
HAProxy - Load balancer
2c672f282d
When a READ or a WRITE activity is reported on a channel, the corresponding date is updated. the last-read-activity date (lra) is updated and the first-send-block date (fsb) is reset. The event is also reported at the channel level by setting CF_READ_EVENT or CF_WRITE_EVENT flags. When one of these flags is set, this prevent the update of the stream's task expiration date from sc_notify(). It also prevents corresponding timeout to be reported from process_stream(). But it is a problem during fast-forwarding stage if no expiration date was set by the stream. Only process_stream() resets these flags. So a first READ or WRITE event will prevent any stream's expiration date update till a new call to process_stream(). But with no expiration date, this will only happen on shutdown/abort event, blocking the stream for a while. It is for instance possible to block the stats applet or the cli applet if a client does not consume the response. The stream may be blocked, the client timeout is not respected and the stream can only be closed on a client abort. So now, we update the stream's expiration date, regardless of reported READ/WRITE events. It is not a big deal because lra and fsb date are properly updated. It also means an old READ/WRITE event will no prevent the stream to report a timeout and it is expected too. This patch must be backported as far as 2.8. On older versions, timeouts and stream's expiration date are not updated in the same way and this works as expected. |
||
|---|---|---|
| .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 | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)