Question about lvs architecture.

[Martijn Grendelman]

Hi,

> i don't understand the need though for session persistence like this;
> i'd expect a centralized session manager (msession for instance) or
> just using a central database for the information would suffice.
> that's how i've been doing it, not sure why everyone has all these
> unique requirements to make sure they can persist sessions across IP
> addresses and AOL proxies and such.

A centralized session manager would be nice, but I for one haven't been 
able to find a decent solution for use with PHP. I don't know about 
other systems or APIs.

Msession is dead (I still have it running, but any attempt to build a 
stable daemon on an up-to-date system failed time after time) and its 
successor (MCache) seems to have died before it even got to beta.

Other projects I have looked at (http://www.vl-srm.net/, for example) 
are also dead, or just aren't suitable (Memcached).

I use Msession for a shared hosting cluster. The main advantage is, that 
  Msession has a PHP extension, so it doesn't require any PHP client 
code.  I need this, because I don't want to implement any dirty hacks 
based on "auto_prepend_file" or something like that, which I would need 
if I'd put my sessions in MySQL.

Well, you can always buy Zend Platform, which features Session 
Clustering, but some of us don't have the $$$.

Any suggestions for alternatives?

Best regards,

Martijn Grendelman








  seems overkill, i've never had a
> problem. of course, i don't know your specific application, but it
> sounds on the level of an HTTP request...
> 
> On 5/9/06, Dan Baughman <dan.baughman at gmail.com> wrote:
>> Internally, ldirectord must make decisions about where to send what
>> connection request, right?  I want to implement a hash table to keep 
>> track
>> of where previous connections from an ip went, and send them to the same
>> server.
>>
>> Previously I was advised to use the CF Scheduler, can anyone elaborate
>> further on that before I start to look at the code?   I need this to
>> maintain that a user will have a persistent session with one user.
>>
>> Any sort of timeout is optional.  Once an ip gets a server it can 
>> always get
>> that same server.  I had previously thougth of giving the session a 
>> timeout,
>> but now I'm leaning towards just having it maintain the hash forever, and
>> I'll just restart the director deamon every night at  2 am (or never).
>>
>> Any pointers?
>> _______________________________________________
>> LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
>> Send requests to lvs-users-request at LinuxVirtualServer.org
>> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
> Send requests to lvs-users-request at LinuxVirtualServer.org
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> 
>