Hey,
I had asked earlier about fixing problems with 504 errors by increasing
timeouts, which helped a great deal. The problem is CPU usage is up to as
high as 100% very frequently, which is worrying me. Is it possible that
something else needs to scaled down with the increase to the queue and
server timeouts?
global
user nobody
group nobody
daemon
maxconn 204800
tune.bufsize 16384 # 16k
tune.rcvbuf.server 141312 # 128k
defaults
mode http
backlog 32768
maxconn 204800
timeout connect 120ms # how long to try to connect to a
backend
timeout queue 10s # how long a request can wait for a
backend before 503ing
timeout server 15s # how long to wait for response from
backend before 503ing
timeout client 60s # how long to wait for data from
clients (exchanges)
timeout http-keep-alive 60s # how long to keep keepalive sessions
when inactive
option abortonclose
no option forceclose
option http-no-delay
option nolinger
frontend openx
bind *:9010
default_backend bidder9010
backend bidder9010
balance roundrobin
server bid001 10.1.1.50:9010 weight 1 maxconn 51200 check
server bid002 10.1.1.112:9010 weight 1 maxconn 51200 check
server bid003 10.1.1.113:9010 weight 1 maxconn 51200 check
server bid004 10.1.1.114:9010 weight 1 maxconn 51200 check
server bid005 10.1.1.115:9010 weight 1 maxconn 51200 check
server bid006 10.1.1.116:9010 weight 1 maxconn 51200 check
server bid007 10.1.1.117:9010 weight 1 maxconn 51200 check
server bid008 10.1.1.118:9010 weight 1 maxconn 51200 check
server bid009 10.1.1.119:9010 weight 1 maxconn 51200 check
server bid010 10.1.1.120:9010 weight 1 maxconn 51200 check
server bid011 10.1.1.127:9010 weight 1 maxconn 51200 check
server bid012 10.1.1.128:9010 weight 1 maxconn 51200 check
server bid013 10.1.1.126:9010 weight 1 maxconn 51200 check
server bid014 10.1.1.203:9010 weight 1 maxconn 51200 check
server bid015 10.1.1.204:9010 weight 1 maxconn 51200 check
server bid016 10.1.1.205:9010 weight 1 maxconn 51200 check
Thanks so much for all your help folks. The only thing I can think is now
with far fewer connections rejected maybe haproxy is becoming more
overloaded?
