Important: Nginx + Haproxy + Mongrel Question

Asif Ali azifali at gmail.com
Thu Nov 20 15:48:02 MSK 2008


Dave,
Each of those servers are 16G RAM, Quad Core, Dual Processor Machines by
Dell. So - the memory shouldn't really be a problem.

Although someone did mention that *ip_conntrack* module might be a problem.

I am not sure what the issue is and not able to understand  - why haproxy is
unable to route requests.

Can you please tell me if there could be some other issue?

regards

Asif


On Wed, Nov 19, 2008 at 6:43 PM, Dave Cheney <dave at cheney.net> wrote:

> Hi Asif,
>
> What fails completely ? HaProxy, Mongrel or Nginx ?
>
> I noticed that 192.168.1.16 for instance had over 50 mongrels assigned to
> it. At an average memory usage of 60-80 meg (just after startup) that is an
> enormous amount of memory in use (if I understand your config correctly), is
> the problem with the underlying server platform? Possibly swapping, or
> spending all its time scheduling processes?
>
> Cheers
>
> Dave
>
>
> On 19/11/2008, at 9:53 PM, Asif Ali wrote:
>
>  We have configured nginx +  haproxy + mongrels [ more than 150 instances].
>> While it works perfectly fine for small configuration, a larger set of
>> mongrels - fail completely.
>>
>> I have attached the configuration file for your reference. Apologies for
>> the inconvenience if this is coming into the wrong list.
>>
>> Thanks in Advance
>>
>> Asif
>> <haproxy.cfg>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20081120/832f5205/attachment.html>


More information about the nginx mailing list