Hi,
I'm observing a strange issue with haproxy 2.4.22 (but it was also on
previous versions).
I have set maxconn to 200000 in global and defaults configuration section
and with following configuration
frontend front
mode http
option http-keep-alive
bind 10.0.0.10:443 ssl crt /etc/cert/crt.pem alpn h2,http/1.1 process
1/1
bind 10.0.0.10:443 ssl crt /etc/cert/crt.pem alpn h2,http/1.1 process
1/2
...
bind 10.0.0.10:443 ssl crt /etc/cert/crt.pem alpn h2,http/1.1 process
1/20
default_backend back
backend back
option http-keep-alive
mode http
http-reuse always
option httpchk GET /health HTTP/1.0\r\nHost:\ ttt.local
http-check expect string OK
timeout queue 1s
default-server maxconn 2000
default-server resolve-prefer ipv4 resolvers default-dns
server slot_0_checker 10.0.0.82:31011 check weight 0 disabled cookie
slot_0_checker
server slot_1_checker 10.0.0.236:31011 check weight 0 disabled cookie
slot_1_checker
server slot_0_0 10.0.0.82:31011 source ${SNAT_741_0} track
slot_0_checker weight 50 disabled cookie slot_0_0
server slot_1_0 10.0.0.236:31011 source ${SNAT_741_0} track
slot_1_checker weight 51 disabled cookie slot_1_0
I'm experiencing a situation in which clients cannot connect (termination
state CQ-- or sQ--) which is expected when the traffic is high (maxconn
2000 on each server) and HAProxy is using much more CPU. However after such
an event when traffic is lower or when I cut off the traffic completely
(cpu idle is almost 100%) I still cannot connect to the proxy. Termination
state is still sQ-- and I receive 503 in response while the stats page and
CLI reports that there are no connections to proxy.
Am I missing something or is it a bug?
Kind regards,
Maciej
