Re: [lvs-users] Fwd: InActConn dilemma

To: " users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] Fwd: InActConn dilemma
From: Graeme Fowler <graeme@xxxxxxxxxxx>
Date: Sun, 14 Feb 2010 09:40:24 +0000
On Sun, 2010-02-14 at 10:16 +0100, Andre Magri wrote:
> Our two servers are the exact same Dell Poweredge model with the same cpu's
> and same memory modules except for the network cards where one of them is
> running in a team.  They are running IIS and I can see from perfmon that one
> of them (www1) is getting a high amount of requests where as the other is
> quite free.

OK, that's good to know. Now we can concentrate on...

> If I observe connections on both servers (ipvsadm -lcn), connections to www2
> are being kept established and therefore further traffic is done through
> these already 'active' connections, listed as ESTABLISHED, until they are
> timed out. www1 (or LVS, I'm getting confused here) is not keeping these
> connections alive and therefore turn into FIN_WAIT state until the 2 minutes
> are up.


> Which one is behaving incorrectly here - www1 or www2?  This will help me
> establish where the problem is.

They're both behaving correctly :)

It looks as though you have IIS on www1 set to not do keepalives so
every request *for every element on a page* is a separate connection.

www2, however, seems to be honouring keepalive requests so is allowing a
given client to make multiple HTTP requests down the same TCP

Both of these are perfectly normal behaviour and are dependent on
circumstance, however it would be easier for you to handle the
connections (in terms of raw numbers, nothing else) if the IIS server on
both systems was configured in the same way.

You might need to check the following:



Please read the documentation before posting - it's available at: mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to

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