mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2025-01-19 12:10:46 +00:00
db2ab8218c
There have been a large number of issues reported with conn_cur synchronization because the concept is wrong. In an active-passive setup, pushing the local connections count from the active node to the passive one will result in the passive node to have a higher counter than the real number of connections. Due to this, after a switchover, it will never be able to close enough connections to go down to zero. The same commonly happens on reloads since the new process preloads its values from the old process, and if no connection happens for a key after the value is learned, it is impossible to reset the previous ones. In active-active setups it's a bit different, as the number of connections reflects the number on the peer that pushed last. This patch solves this by marking the "conn_cur" local and preventing it from being learned from peers. It is still pushed, however, so that any monitoring system that collects values from the peers will still see it. The patch is tiny and trivially backportable. While a change of behavior in stable branches is never welcome, it remains possible to fix issues if reports become frequent. |
||
---|---|---|
.. | ||
design-thoughts | ||
internals | ||
lua-api | ||
51Degrees-device-detection.txt | ||
acl.fig | ||
architecture.txt | ||
close-options.txt | ||
coding-style.txt | ||
configuration.txt | ||
cookie-options.txt | ||
DeviceAtlas-device-detection.txt | ||
gpl.txt | ||
haproxy.1 | ||
intro.txt | ||
lgpl.txt | ||
linux-syn-cookies.txt | ||
lua.txt | ||
management.txt | ||
netscaler-client-ip-insertion-protocol.txt | ||
network-namespaces.txt | ||
peers-v2.0.txt | ||
peers.txt | ||
proxy-protocol.txt | ||
queuing.fig | ||
regression-testing.txt | ||
seamless_reload.txt | ||
SOCKS4.protocol.txt | ||
SPOE.txt | ||
WURFL-device-detection.txt |