|
At 11:35 AM 18/11/2003 +0900, you wrote:
On Tue, Nov 18, 2003 at 11:18:37AM +1100, Guy Waugh wrote:
> Hi all,
>
<snip>
Hi,
I think that you are confused between the concept of persistance and
connection-timeouts. Persistance effects which real server LVS will
choose for new connections. If persistance is in effect and the
persistant-timeout has not expired then the same real server will
be used for subsequent connections from the same CIP. But in
your case you only have one real server so persistance is a moot point.
You are correct in asserting that the CIP:0 entry you see
is a master entry. Actually in the code it is refered to as a template.
When a new connection comes in LVS looks for VIP:Vport+CIP:0. If it is present
then it will use the attached RIP:Rport. If not it just chooses
one of the available real servers as per the scheduling algorithm
that is in effect. But again this is a moot point, as you only have
one real server.
The CIP:0 entry does not acctually represent
a connection at all. Just a template for creating new connections. Its
timeout should be set to the persistance-timeout each time the template
is used to create a new connection.
The other entries are the connections themselves. Their timeouts
are set by the various timeouts that can be manipulated through
/proc/sys/net/ipv4/vs/timeout_*. This is where the value of
900 seconds comes from. __It has nothing to do with persistancy__
Ah-hah! Thanks Horms, that cleared it up for me... I was definitely
confusing persistence with TCP timeouts etc.
Cheers,
Guy.
As per the HOWTO entry you listed above, some of these values can
also be manipulated using ipvsadm --set
--
Horms
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
