Hello Willy,

Thanks you for your kind response.

Here are the information required ::::

Haproxy version :
HA-Proxy version 1.5.8 2014/10/31
Copyright 2000-2014 Willy Tarreau <[email protected]>



If this can help As you have already responded to two other scenarios :

http://www.serverphorums.com/read.php?10,1075864

http://t55696.web-haproxy.webtalks.info/100-cpu-load-t55696.html

how can we "exactly" trace if we have issue similar.

ELSE :

Attached is the haproxy config.  Kindly guide us. Thanks a lot in advance.

Even small suggestions are very much appreciated.

Thanks & Regards
Saurab


On 3/19/2015 12:33 PM, Willy Tarreau wrote:

Hello,

On Thu, Mar 19, 2015 at 11:04:54AM +0530, Saurabh Tiwari wrote:

Hello,

we are facing issue of haproxy consuming 100% CPU , we tried different
tunings on haproxy cfg . But only solution remains is of making the
nbproc > 1, which is not a permanent solution.

_Pasting the common config section:_
global
        maxconn 280000
        nbproc  1
        user    haproxy
        group   haproxy
        chroot  /var/lib/haproxy
        stats   socket    /var/run/haproxy.sock

defaults
        mode    http
        balance roundrobin

        maxconn                 275000
        timeout connect         5000
        timeout server          50000
        timeout client          50000

        timeout http-keep-alive 5s
        timeout http-request    15s

        retries 3
        option  redispatch
        option  abortonclose
        option  tcp-smart-accept
        option  tcp-smart-connect
        #option splice-auto

listen stats self.prv:x0x0x
        stats   enable
        stats   uri     /

Your config is truncated, you only list the stats page, I guess you're
not running at 100% with a stats page only, so would you please post
your complete config (remove any password or sensitive info, hide IP
addresses if you wish).

Please also give some information such as the request and/or connection
rate, traffic type (mostly SSL, etc).


Kindly suggest, any solution possible. We need fix badly , do not wish
to migrate to nginx just for this reason.

That doesn't make sense, if you switch from one product to another every
time you're facing a configuration problem, you can switch often! If you
need features that you only find in nginx, sure you'd rather switch, but
if the features you need are in haproxy, in general you should get better
performance here so switching will make the situation worse.

Willy

Attachment: haproxy.conf
Description: Binary data

Reply via email to