[horde] still having problems with dropped sessions

[Kevin Konowalec]

Okay I've added 4 machines with 1.5 Gigs each dedicated to  
memcached.  I just added them to the list so the original memcached  
boxes are still in the loop... so I have a total of 7Gb dedicated to  
it which I'm sure is complete overkill but if it works I'll be  
pulling the original ones out and leaving 6Gb in.

BUT not long after I added the other machines in I was getting  
complaints about people being booted again.  I'm thinking that's  
likely due to them having logged in before I made the changes and  
thus they didn't get the conf file changes and so are locked to the  
original 2 machines for the remainder of their session.  Does that  
sound reasonable?  Or could there be something else?


On Mar 14, 2007, at 3:25 PM, Michael M Slusarz wrote:

> Quoting Kevin Konowalec <webadmin at ualberta.ca>:
>
>> Yeah that's exactly what I was thinking... that's why I was asking
>> how much session data is actually stored per user so I can estimate
>> accordingly.
>
> it definitely is not unheard of that IMP-specific sessions can be
> greater than 1 MB each.  So you should plan accordingly.
>
> A lot of the session size concerns has been addressed in HEAD - from
> reducing the amount of session data to limiting the size of viewable
> MIME parts to using in-memory compression to reduce the storage size
> of Horde_SessionObjects.
>
> michael
>
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
>
> -- 
> Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>