mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-06 18:01:05 +01:00
f5cab82025
When I/O events are being processed, we want to make sure to mark the thread as not stuck. The reason is that some pollers (like poll()) which do not limit the number of FDs they report could possibly report a huge amount of FD all having to perform moderately expensive operations in the I/O callback (e.g. via mux-pt which forwards to the upper layers), making the watchdog think the thread is stuck since it does not schedule. Of course this must never happen but if it ever does we must be liberal about it. This should be backported to 2.0, where the situation may happen more easily due to the FD cache which can start to collect a large amount of events. It may be related to the report in issue #201 though nothing is certain about it.
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)