|
Didn't I just read about this kind of persistence, needed for the https
protocol. Maybe I read this on the ultra-monkey site, or linux-ha.org, or the
LVS site...
I think this is just a matter of configuring lvs.
Nicolas Huillard
-----Message d'origine-----
De: Shez [SMTP:shez@xxxxxxx]
Date: jeudi 11 mai 2000 15:30
À: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Objet: Policies based on packet content
Hi there,
What I want to achieve is HA and load balancing for a web-farm handling
many thousands of different sites. For a variety of efficiency and
performence reasons I want to have a form of persistance based on the ``Host:''
header of the incoming packets.
In this way during normal usage requests for a particular site would always end
up at the same backend server. Normal usage is here defined as when load is
acceptable and no failures have occured.
Now I understand that LVS makes most of its decisions in kernel space, and
this sort of data based filtering generally is better off living in user space,
but I also know that the standard kernel masquarading does some work of this
type, for example for re-writing ftp command streams.
So basicaly I'm curious to see if anyone thinks that this sort of scheme will
ever work in LVS, or whether I should go off investigate high-performence
userland relays?
Cheers
Shez
--
NSL NET Ltd, 26 Forth Street, Edinburgh, EH1 3LH, UK
tel + 44 (0)131 477 8215 fax + 44 (0)131 477 8223 http://www.nsl.net
|
