|
Just my 2 cents :
I continuously hear on this list suggestions to rewrite applications to use
other session management means then the one that comes with IIS. As a
Windows/Unix developer/administrator (you can mix and match any one of the 2
groups ;), i would really like to say, that usually this is not that easy in
the IIS environment, especially if you try to tell this to windows only
developers, that don't know anything else then the MS way to do things. The
best they can hope is to wait for the upcoming IIS 6 release, that includes
session management that is meant to use in webfarms (db based), or to try
some non microsoft (still proprietary) solutions, that try to do the same,
like frameWERKS framework, that functions as a drop in replacement for the
IIS session components.
I am not saying this to start a MS war on the list, but only to tell, that
when an ms inclined person hears that he should "re-write the application" -
95% chance that this will be his last try to use lvs for his solutions. on
the other hand, saying that there is a such and such solution that can help
him will probably be considered...
Alex.
-------Original Message-------
From: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Date: éåí ùéùé 22 ðåáîáø 2002 18:11:24
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: HTTP(s) persistence
devendra orion wrote:
>
> The website is hosted on win2000 and
> uses IIS session Mgmt (no cookies).
I don't know anything about IIS session mgmt.
If this would be useful to others setting up an LVS,
could you give us some more info about it? Thanks
> 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?
8hrs = 8 * 60 * 60 sec = some_number
ipvsadm -A -t VIP -p some_number
you are probably going to handle tcp timeouts as well
(see postings in the last week and in the HOWTO).
The best solution is not to use persistence, but to re-write
the application, so that the state information is stored
in a place accessable to all realservers. In this way,
if one realserver fails, the session with the client can continue.
(see the section in the HOWTO on persistence).
Joe
--
Joseph Mack PhD, Senior Systems Engineer, SAIC contractor
to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
_______________________________________________
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
.
|
