Project

General

Profile

Actions

Bug #11756

open

HaProxy does not transfer backend states during reload

Added by Florian Apolloner 6 months ago. Updated 2 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
haproxy
Target version:
-
Start date:
03/30/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

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.

Actions #1

Updated by Viktor Gurov 6 months ago

fixed in haproxy-devel: #10599

Actions #2

Updated by Florian Apolloner 6 months 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.

Actions #3

Updated by Viktor Gurov 5 months ago

  • Affected Version deleted (2.4.5-p1)
Actions #4

Updated by Jim Pingle 5 months ago

  • Status changed from New to Pull Request Review
Actions #5

Updated by Renato Botelho 2 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Viktor Gurov

PR has been merged. Thanks!

Actions

Also available in: Atom PDF