Thanks for the info.
I'm just not sure how we'd fix this since the process monitor we run is only intended to catch cases where a daemon exits, not when it's misbehaving.
Can you take a look at this discussion and make sure you have a version of haproxy >= 1.8.15 ? Seems someone else had a similar problem with it?
https://discourse.haproxy.org/t/haproxy-stops-serving-frontend-requests-while-not-closing-backend-connections-at-100-cpu-utilisation/3292/8
Thanks for the info.
I'm just not sure how we'd fix this since the process monitor we run is only intended to catch cases where a daemon exits, not when it's misbehaving.
Can you take a look at this discussion and make sure you have a version of haproxy >= 1.8.15 ? Seems someone else had a similar problem with it?
https:/ /discourse. haproxy. org/t/haproxy- stops-serving- frontend- requests- while-not- closing- backend- connections- at-100- cpu-utilisation /3292/8