RE: 2.6 kernel tuning for haproxy

The stats are not showing any problems with prize_media (at least no worse than blobzone). It was only up for a little over 2 hours, was that long enough for the problem to have shown up? Even if it is a TCP tuning issue, I would expect the problem to show on the stats better, instead of just on incoming connections. The only thing I notice is the max sessions is going rather high, so make sure you back-ends will hold that many open. (ie: apache defaults to only 150, and any over 150 will just sit in the OS queue until others free up). Is there any chance there is a state-full firewall in the picture (especially between client and haproxy) that could be complicating the issue?      

From: Matthieu Huguet [mailto:matthieu_huguet#prizee.fr] Sent: Wednesday, November 07, 2007 10:26 AM To: Lauro, John; haproxy#formilux.org
Subject: RE: 2.6 kernel tuning for haproxy    

> A couple of quick questions...

> What's your stats page look like on the proxy?

> If you bypass the proxy and connect directly to the backends, are
they fine? Do you have the same configuration for the backends and the proxy?  

The stats page look like this:
http://img131.imageshack.us/img131/212/haproxystatsvi1.png

If I connect directly to the backends, it works fine.

The configuration is the same for the backends and the proxy.  

Some comments on the stats page:

• Haproxy works with "nbproc=4" so it's one of the four stats pages.
• The frontend/backend "blobzone" is binded on one virtual IP. It works in HTTP mode. There is no connection problem with this IP.
• The section "prizee_media" is binded on another virtual IP, in TCP mode. The connection establishment problem is only for this IP.
• The two virtual IPs are sharing one physical interface.