|
Hmm... My suggestion uses a little URL redirection. ;-) Just a bit.
Would this work?...
N.B. VS-NAT won't really work with the following arrangement. Realservers
need real IP addresses.
1. First Client request goes to http://www.foo.com/
2. LVS catches this and does whatever scheduling algorithm.
3. Realserver-01 receives the request. Apache rewrites the URL to
http://www-realserver-01.foo.com/
4. Response is sent directly from Realserver to Client.
5. Subsequent client requests go directly to Realserver, bypassing LVS.
e.g. http://www-realserver-01.foo.com/blah/blah/blah; but are NOT rewritten
by Apache. N.B. Not load balanced by LVS.
This is basically a RR-DNS via LVS strategy because the next time the
client asks for http://www.foo.com/ -- LVS will do its thang.
So as long as no-one bookmarks pages. You are cool. ;-)
On Thu, Nov 30, 2000 at 04:21:55PM -0000, Andy Marsh wrote:
> We must allow balancing of the first request from
> the client, every subsequent request then being
> sent to the same server. Without using some form
> of URL redirection (make each backend server have
> all served pages have a specific url in them, eg.
> http://www.foo.com/server1/xxx/xfd/d) is there are
> way to do this?
--
B. http://makelinux.org/ "Always real." http://realthought.net/
__________________________________________________________________________
We're mortal -- which is to say, we're ignorant, stupid, and sinful --
but those are only handicaps. Our pride is that nevertheless, now and
then, we do our best. A few times we succeed. What more dare we ask for?
-- Ensign Flandry
|
