Re: node frequently goes down on another physical machine

Hi, Thanks a lot for a helping hand!! As per the suggestion I have upgraded to 1.4.10. Now it took the option tcp-smart-accept and tcp-smart-connect. But still i am seeing lots of retries, and the processes running on remote server several times timeout estabilishing http connection. Followin

Re: Help with high concurrency and throughput configuration

Hi Cyril, On Wed, Dec 22, 2010 at 7:33 PM, Cyril Bonté wrote: > Hi Joubert, > > Le mercredi 22 décembre 2010 22:11:27, Joubert Berger a écrit : >> (...) >> > For the proxy I am comparing squid (as a reverse proxy) and haproxy. >> >> For squid, the only major thing I added was: >> max_filedesc 327

Re: node frequently goes down on another physical machine

Hi, first upgrade to a more recent build of haproxy 1.4.x would be better. Also you should send us more info of your hearbeat config and haproxy so that we can understand better your setup. Bye Amit Nigam a écrit : Hi, We have just recently migrated from apache to HAProxy. We are having 2

node frequently goes down on another physical machine

Hi, We have just recently migrated from apache to HAProxy. We are having 2 tomcat(TC1 and TC2) nodes along with 2 LB(LB1 LB2) nodes and other DB nodes. We created 4 virtual servers out of one physical server. Using 2 servers we have 8 nodes. We are running two HAProxy instances on LB1 and LB2 on

[PATCH] add pattern extraction method to stick on query string parameter values (2nd version)

(there seems to be recurrent problems for my email to get through the mailing list - would it be possible for an admin to check emails coming from this adress ?) Hi, This is an updated version of my patch for url parameter extraction on stick table. It improves on most issues + a minimal doc for