RE: encounter a problem when testing HAProxy

2012-08-15 Thread jerry liu

I finally found that, it's because the back-end Apache server is not enough, 
when I added more Apache servers in the back-end, haproxy can handle more 
requests per second. Thanks guys. I think I can close this case.

> Date: Wed, 15 Aug 2012 10:28:40 +0200
> Subject: Re: encounter a problem when testing HAProxy
> From: bed...@gmail.com
> To: jerrythrill...@hotmail.com
> CC: mandm_z...@yahoo.com; haproxy@formilux.org
> 
> Hi,
> 
> Amol forgot to mention it, but the conntrack table full should appear
> on the LB, not on the servers.
> 
> Could you paste here a few log lines from when the problem occurs?
> HAProxy logs are very verbose and we may find something here.
> 
> Which version of HAProxy are you running?
> 
> cheers
  

RE: encounter a problem when testing HAProxy

2012-08-14 Thread jerry liu

I didn't find this error message in /var/log/messages on any of these three 
servers. Thanks for your advice, is there any possibility that could cause this?

Date: Tue, 14 Aug 2012 13:43:24 -0700
From: mandm_z...@yahoo.com
Subject: Re: encounter a problem when testing HAProxy
To: jerrythrill...@hotmail.com; haproxy@formilux.org

Check your /var/log/messages, you must be hitting a  “nf_conntrack: table full, 
dropping packet” error
From: jerry liu 
 To: haproxy@formilux.org 
 Sent: Tuesday, August 14, 2012 9:05 AM
 Subject: encounter a problem when testing HAProxy
   





Hi, When I was doing a test with HAProxy, I bumped into a problem, I didn't 
know why it happened, I wish you could help me out. Here's the scenario, I set 
up HAProxy on server A and apache on server B, I used gatling as the test 
client that was running on server C to send 1000 requests per second to 
HAProxy, I noticed that, the current sessions is growing rapidly and when it 
hit around 9000, the gatling client got the "connection timed out" error.
 Below is the conf of the HAProxy I was using and attached is the 
screenshots that shows the status of HAProxy from the beginning of starting 
test client to the time when the error happened. I'm looking forward to hearing 
from you soon. 
globallog 127.0.0.1   local0maxconn 131086   
 daemon<
 div>stats socket/tmp/haproxy.sock
defaultslog globalmodehttpoption  httplog   
 option  httpcloseoption  dontlognulloption  abortonclose   
 log 127.0.0.1 local3retries 3option  redispatchmaxconn 
131086timeout connect 2contimeout  5
clitimeout  5srvtimeout
  5
listen web_proxy  ip address of Server A   mode http   balance 
roundrobin#   cookie SERVERID insert indirect nocache#option 
httpchk HEAD /index.html HTTP/1.0server webA   ip address of Server B   
 stats enablestats hide-versionstats uri /haproxy-stats 
   stats realm Haproxy\ statisticsstats auth admin:adminstats 
refresh 3sstats admin if TRUE