Re: web replication
- From: fusillo <fusillo@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 09 Aug 2006 03:27:19 +0200
ed ha scritto:
to enable the http session information i think about using a network
filesystem placed on backend and setting the mount point as a session
directory path (using the php session's configuration directive)
the cookies should not be a problem, should it?
Session cookies relate to memory in the server, so if it's a session
cookie, then yes it's a problem if one cannot be certain of which box
the client is going to connect to in 5 mins time.
yes but it's this the reason to use a shared memory for the session
information. Get it by mounting the same nfs (placed phisically in the
backend) in the path used to save the session dictionary in every single
i wouldn't play with layer 7, my idea is using a layer 4 load bilancingcookies resides in the client browser and forwarded to the server
based on domain name (the bilancer domain name).
to replicate the db i would use a simple master slave mysql
This depends on your balancing device, some are full protocol proxies
which can do exactly as you ask. I think there's one called 'pound'
which is GNU that can do this for you.
, i'm actually studying the lvs documentation, ipvs via nat use nat to
traslate the virtual service ip(the ip of the web bilancer) to one real
server ip, choosing the server by means of a given scheduling algoritm.
if the cookie's domain matches the virtual service ip when a browser
send it in a http header it will be forwarded and bilanced to the real
server thanks a lvs nat rule, it shouldn't be important what server
because the session information is shared by the servers.
could it run?
thanks i will read about it.the unsolved problem is bilanced the https session, a session must use
the same server because there's an handshake for the simmetric key
Pound does this I think, also look into source/dest hashing on the NAT
how do you recognize a single https session from another https
session? the actual idea is not shape this traffic and dedicate one
server for the ssl traffic using port for the nat prerouting rule.
It's the NAT host that solves this through the socket (sourceip,destip,
sourceport,dstport) that makes what we know as a socket. The socket is
matched against the NAT table.
maybe using a right sized hash table i can force it passing to the same
real server but it depends about traffic volume.
- Re: web replication
- From: fusillo
- Re: web replication
- Prev by Date: Continuation of "Arrrgh! rsync "chroot failed" error message!"
- Next by Date: Re: web replication
- Previous by thread: Re: web replication
- Next by thread: Re: web replication