Willy Tarreau
fce77910e5
MINOR: sink/ring: rotate non-empty file-backed contents only
If the service is rechecked before a reload, that may cause the config to be parsed twice and file-backed rings to be lost. Here we make sure that such a ring does contain information before deciding to rotate it. This way the first process starting after some writes will cause a rotate but not subsequent ones until new writes are applied. An attempt was also made to disable rotations on checks but this was a bad idea, as the ring is still initialized and this causes the contents to be lost. The choice of initializing the ring during parsing is questionable but the config check ought to be as close as possible to a real start, and we could imagine that the ring is used by some code during startup (e.g. lua). So this approach was abandonned and config checks also cause a rotation, as the purpose of this rotation is to preserve latest information against accidental removal. (cherry picked from commit 32872db6050cf39bf8ba80e40a2b6c4ee184a8e6) Signed-off-by: Willy Tarreau <w@1wt.eu>
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)
Description
Languages
Shell
100%