Re: Session and Multi Server Architecture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



mike wrote:

>> Check out persistency in LVS for instance:
>> http://www.linuxvirtualserver.org/docs/persistence.html
> 
> i know persistence handling is an option in LVS, but i haven't seen
> the need to use it. i use LVS right now without even bothering with
> any of that.

Because you've chosen another option - memcached presumably - which is
more expensive over all.  (IMHO).

> besides, if you are sticking a user on the same server, what happens
> when that server dies? 

On the next request, LVS will know not to try that server, and the user
will move to another one.  Obviously the session-context will die, but
is that really a big deal?  How often does one of your servers die? 
Sure, if you've got 10,000 in a cluster, you'll have fans and harddisks
pop every so often, but I have my doubts about memcached scaling to
that level (please correct me if I'm wrong here, I have _no_ experience
with memcached). 

> possible connection stampedes to others, their 
> session info and experience is trashed (unless LVS migrates it fast
> enough)

LVS won't migrate any of your data for you.  It'll shift the client to
an available server, that's all. 


/Per Jessen, Zürich

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux