Control: tags -1 upstream fixed-upstream

This has now been fixed upstream with commit 41275a691 (MEDIUM: init: 
set default for fd_hard_limit via DEFAULT_MAXFD, 2024-07-03).

On a side-note, this was triggered by a recent change in systemd[1], 
which now sets the hard RLIMIT_NOFILE limit to the kernel max value 
(2^30 - 8). HAProxy would then a) bump the soft limit to the hard limit 
and b) in the absence of maxconn/maxsock, use the new (soft) limit to 
calculate how many file descriptors it can possibly hold and size the 
file descriptor table accordingly. This file descriptor table would then 
be allocated and initialized, eating a lot of CPU cycles and GBs of 
memory in the process.

The fix is marked to be backported all the way back to 2.6, so the next 
uploads to unstable will probably be fixed. Until then, as suggested in 
my previous message, users are advised to explicitly set global.maxconn 
to a sane value, especially on testing.

Cheers,
Apollon

[1] https://lists.debian.org/debian-devel/2024/06/msg00041.html

Reply via email to