On Thu, Mar 11, 2010 at 4:03 AM, TheOnly92 <05049...@gmail.com> wrote:
> We used memcache as a session storage server because we needed to > balance load across servers and share session data. Persistent file > storage is not usable, and since memcache session storage is easy to > configure in PHP, so we have decided to use it. > Hard to argue with that. As I said before, though, it might be worth looking into TokyoTyrant. It speaks memcached and it's persistent, so you can basically drop it in and start using it with your application code as it exists. It's not as fast or lightweight as memcached, though, so I would suggest using it only as an add-on in situations where persistence is important. > Before this, memcache maximum storage was set to 64 MB, the data went > up to 54 MB and so we thought it was the cause of cache misses. But > after we increased to 256 MB, the problem is still occurring. Users > report that after they logged in, they click on another page and they > get logged out. But after a refresh they appear logged in again. > > session.gc_maxlifetime 1440 1440 > This is definitely unusual behavior. Have you tried debugging it at all? I'd say that you should try going through step-by-step and checking the value that's stored in memcached at each point. Given what you described, it sounds to me like the bug is on the application side, not in memcached-- it sounds like some sort of state is perhaps being stored and that's why they see themselves as logged-out until they do a refresh. -- awl
