Bug #11756
open
HaProxy does not transfer backend states during reload
0%
Description
When reloading Haproxy (due to config changes for instance) the newly started process does not seem to remember the existing backend status.
The generated haproxy config does contain: server-state-file /tmp/haproxy_server_state
and the haproxy packages writes the server state before reloading: https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-haproxy/files/usr/local/pkg/haproxy/haproxy.inc#L2344-L2345
but it seems to miss the configuration to actually load those during start: https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#load-server-state-from-file
Now I wonder if this is on purpose or if this is an oversight. I added "load-server-state-from-file global" to the defaults section and manually reloaded haproxy and all backends kept their previous state.
Updated by Florian Apolloner over 3 years ago
Hi Viktor, I do not think that the ticket you linked is correct. I am specifically talking about the config option "load-server-state-from-file global". I do know that hitless reloads work (even on stable), but it doesn't seem that the backend check status is transferred over to the new instance.
Updated by Viktor Gurov over 3 years ago
- Affected Version deleted (
2.4.5-p1)
Updated by Jim Pingle over 3 years ago
- Status changed from New to Pull Request Review
Updated by Renato Botelho over 3 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!