Re: CPU saturated with 250Mbps traffic on frontend

Lukas, thank you for pointing to possible keep-alive issues, I've tested it before, but did it again just to make one more check! I've increased keep alives timeout to 10se and removed http-server-close, restarted haproxy :) Changes I've noted - haproxy reduced from AVG 78% to AVG 75% per each

Re: CPU saturated with 250Mbps traffic on frontend

Evgeniy, On 4/5/2015 4:47 PM, Evgeniy Sudyr wrote: Lukas, thank you for pointing to possible keep-alive issues, I've tested it before, but did it again just to make one more check! I've increased keep alives timeout to 10se and removed http-server-close, restarted haproxy :) Changes I've

Re: Gracefull shutdown

❦ 5 avril 2015 09:33 GMT, Cohen Galit galit.co...@comverse.com : Hello HAProxy team, How can I perform a graceful shutdown to HAProxy? I mean, not by killing process with pid. You can send the USR1 signal. HAProxy will stop once all connections have been closed. -- The devil can cite

RE: CPU saturated with 250Mbps traffic on frontend

Hi all, haproxy is used for http and https load balancing with TLS termination on haproxy side. I'm using openbsd -stable on this box. I got CPU saturated with 250Mbps traffic in/out summary on frontend NICs and 3000 ESTABLISHED connections on frontent interface to haproxy. Remove:

Gracefull shutdown

Hello HAProxy team, How can I perform a graceful shutdown to HAProxy? I mean, not by killing process with pid. Thanks, Galit This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse

Re: Gracefull shutdown

On 5 April 2015 at 10:33, Cohen Galit galit.co...@comverse.com wrote: How can I perform a graceful shutdown to HAProxy? I mean, not by killing process with pid. Please could you describe the behaviours you expect from a graceful shutdown which you don't get from killing the process? I would

CPU saturated with 250Mbps traffic on frontend

Hi all, haproxy is used for http and https load balancing with TLS termination on haproxy side. I'm using openbsd -stable on this box. I got CPU saturated with 250Mbps traffic in/out summary on frontend NICs and 3000 ESTABLISHED connections on frontent interface to haproxy. # all connections to

Re: CPU saturated with 250Mbps traffic on frontend

Nenad, thank your answer! 1) this is only Haproxy server active (active/passive config exists, but using carp on OpenBSD). 2) As I understand with nbcproc 4 I can't get stats working correctly ... however at the moment I see that for https frontend I have : Current connection rate:58/s