Re: LVS chokes on 600+ connections

To: ataranchenko@xxxxxxxxxxxxx, <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: LVS chokes on 600+ connections
From: Horms <horms@xxxxxxxxxxxx>
Date: Fri, 26 Aug 2005 12:56:47 +0900
On Thu, Aug 25, 2005 at 09:51:18AM -0400, Andrei Taranchenko wrote:
> We have an active director with 256 MB RAM, and two nodes.
> When I do a stress test, the client starts getting timeouts when the
> number of *inactive* connections hits 600 or so. If I take out a node,
> the same number of inactive connections is easily handled by a node, but
> it is still a problem for the director.
> The nodes and the director are connected on the hub, and the director is
> the default gateway. The nodes are also connected to the rest of the
> network on the other interface (they need to see the database, etc).
> Can this be a RAM issue?

Perhaps there is some issue with the kernel's network stack, and it
could be resolved by trying a different version. 256Mb of ram should be
able to handle a lot more than 600 connections (they consome 100 or so
bytes each). That is, unless your box is very low on memory for other 
reasons. I've done tests with LVS going up to 3,000,000 connections,
on boxes with around 512Mb or ram (I don't remember exactly), so it
shouldn't be an LVS problem.


<Prev in Thread] Current Thread [Next in Thread>