d9729da982
If two peers are disconnected and during this period they continue to process a large amount of local updates, after a reconnection they may take a long time before restarting to push their updates. because the last pushed update would appear internally in futur. This patch fix this resetting the cursor on acked updates at the maximum point considered in the past if it appears in futur but it means we may lost some updates. A clean fix would be to update the protocol to be able to signal a remote peer that is was not updated for a too long period and needs a full resync but this is not yet supported by the protocol. This patch should be backported on all supported branches ( >= 1.6 )
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)