|
Horms,
Thanks for posting this patch, it is greatly appreciated! It seems to
be
working fine in my testing. Sorry I didn't post my results in a more timely
fashion. I had been reassigned to a different task for the last several
weeks.
Thanks again,
Jeff
-----Original Message-----
From: lvs-users-admin@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-admin@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Horms
Sent: Thursday, July 11, 2002 12:58 PM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: FW: ldirectord and failure of real servers
On Wed, Jul 10, 2002 at 02:11:47AM -0400, Jeff wrote:
> Hello,
> I noticed this thread from last year where the quiecent option was added
to
> ldirectord.
>
> I have the exact situation mentioned below concerning persistence.
> Unfortunately, an application used by clients to my LVS requires long
> persistent connections. (User sessions can stay alive even though the
user
> is inactive for periods up to 45 minutes.)
>
> Is there a way to configure ldirectord to remove the real server
> entirely instead of changing the weight to zero? I would like to
> trash any existing connections if a web server dies. Otherwise, the
> users previously attached to the dead server will have to wait until
> the persistence time elapses (45 minutes) prior to establishing a new
> connection. That could mean a large number of people are out of
> business for an extended period even though the LVS is really still
> operational.
My feeling is that the best way to tackle this would be for the LVS
kernel-code to expire the template used internally for persistent
connections if its real server is set as quiescent.
That said, I think that it is reasonable for ldirectord to have an
option to delete real servers or make them quiescent. Please try the
attached (under-tested) patch which adds a quescent option to the
ldirectord configuration file. The default is for this to be "yes",
setting it to "no" either globably, or within a virtual should give the
behaviour that you are after.
--
Horms
|
