|
When you create your service add the "-p" option with a timeout value. You
don't need to have it persist for 8 hours per se since (AFAIK) persistence
only comes into effect when a person has not sent a request. In other words
persistence does not start from the first connection and last X seconds it
last X seconds after the last packet has been sent. LVS then resets
persistence if the next request is sent BEFORE X seconds has lapsed. This is
how I understood it ... so here is what you would do with your service:
ipvsadm -A -t $VIP:80 -p $SECONDS_OF_PERSISTENCE -s $SCHEDULE
Hope this helps!
--Joe
--
Joe Stump
http://www.joestump.net
----- Original Message -----
From: "devendra orion" <dev_orion@xxxxxxxxx>
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, November 22, 2002 10:15 AM
Subject: HTTP(s) persistence
> Hi!
>
> I need to enable loadbalancing on our curent director
> M/c (LVS-NAT enabled). We are currently having 3
> realservers serving same website and need to be
> loadbalanced. The website is hosted on win2000 and
> uses IIS session Mgmt (no cookies). Only problem is we
> need to keep this session alive for basically 8 hrs as
> our clients access the application continuously. So
> how can i configure the loadbalancer to keep the
> connection persistence to same server after successful
> client login? I am totally confused and basically in
> need of help desperately.
> Please do ask if need any detailed explaination on
> probs.
>
> Thank you
> deven
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
> _______________________________________________
> 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
>
>
>
|
