mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-25 14:12:13 +00:00
haproxy public development tree
4b1a7ea66c
When a resync is needed, a local resync is first tried and if it does not work, a remote resync is tried. It happens when the worker is started for instance. There is a timeout to wait for the local resync, except for the first start. And if the local resync fails or times out, the same timeout is applied to the remote resync. This one is always applied, even if there is no remote peer. On the other hand, on reload, if the old worker has never performed its resync, it does not try to resync the new worker. And here there is an issue. On the first reload, when there is no remote peer, we must wait for the resync timeout expiration to have a chance to resync the new worker. If the reload happens too early, there is no resync at all. Concretly, after a fresh start, if a reload happens in the first 5 seconds, there is no resync with the new worker. The issue only concerns the first reload and affects the second worker. To fix the issue, we must only skip the remote resync if there is no remote peer. This way, on a fresh start, the worker is immediately considered as resync. The local reynsc is skipped because it is the first worker and the remote resync is skipped because there is no remote peer. This patch must be backported to all stable versions. |
||
---|---|---|
.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)