mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-24 04:11:02 +01:00
b8e0fb97f3
The ring's CLI reader unlocks the read side of a ring and relocks it for writing only if it needs to re-subscribe. But during this time, the writer might have pushed data, see nobody subscribed hence woken nobody, while the reader would have left marking that the applet had no more data. This results in a dump that will not make any forward progress: the ring is clogged by this reader which believes there's no data and the writer will never wake it up. The right approach consists in verifying after re-attaching if the writer had made any progress in between, and to report that another call is needed. Note that a jump back to the beginning would also work but here we provide better fairness between readers this way. This needs to be backported to 2.2. The applet API needed to signal the availability of new data changed a few times since then.
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)