max persistance time?

Joseph T. Duncan duncan at engr.orst.edu
Wed Aug 30 21:50:42 BST 2006


>> Hi all,
>> 
>> Is there a max persistance time?
>
> probably a 32 bit counter
>
>> Is this configurable
>
> man ipvsadm

;p nothing in the man page about the "maximum value possible for 
persistance". Also nothing in the howto that i can find, hence my 
asking... if it is a 32bit counter then thats cool. its still not 
mentioned anyware in the man page so...

>
>> I need a persistance time of 1 day. (yes very very huge compared to what is 
>> normaly set) but longest time a session seems to stay is about 10min~ and 
>> then the session is droped
>
> the tcp connection is probably timing out underneath you. look for tcp 
> keepalives in the HOWTO. Otherwise the server could be timing out the client
>
>> I need a long persistance time cause a user may leave his/her terminal 
>> server session running, and return to it the next working day.
>
> persistence only affects the opening of the next tcp connection (ie if you're 
> using a browser to visit a website and you want all your connections to go to 
> the same realserver).
>
> Your problem is that the session is timing out on you.

yup i understand this..

client <--> director session dies and is being timed out. i want the "next 
tcp connection" up to 1 day later to connect back to the same realserver.

however ipvs drops the entery in the inactive connect after 10~ minutes. 
but the user proccesses on the realserver keep going... up tell 1 day 
later (hence the need for a 1 day persistance.)

a new tcp connection to the real server gives the client an auth window, 
after authenticating the session all of the proccesses owned by that 
user are then assosciated with the new tcp session (all standard remote 
desktopy stuff that has nothing to do with ipvs)


is it safe to adjust the tcp_keepalive values? or will i do more havoc 
then good?

*snip*
tcp_keepalive_time - INTEGER
         How often TCP sends out keepalive messages when keepalive is 
enabled.
         Default: 2hours.

tcp_keepalive_probes - INTEGER
         How many keepalive probes TCP sends out, until it decides that the
         connection is broken. Default value: 9.

tcp_keepalive_intvl - INTEGER
         How frequently the probes are send out. Multiplied by
         tcp_keepalive_probes it is time to kill not responding connection,
         after probes started. Default value: 75sec i.e. connection
         will be aborted after ~11 minutes of retries.
*snip*


thanks,
-joseph
_________________________________________________________________________
Info:                           Email:
Joseph T. Duncan                duncan at engr.orst.edu
109 Kidder Hall
Corvalis Or 97333


Search lvs-users Archives
Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort

More information about the lvs-users mailing list