Hi, I'm trying to follow this thread on my mobile, i hope i didn't miss anything. But AFAICS it was not yet explained, when memcached might drop cached data as long as there's enough memory and expiration is not reached. Or is this not deterministic at all? Perhaps you can point me to resources providing more details on this?
Cheers, Martin 2010/3/11, Jérôme Patt <jerome.p...@googlemail.com>: > TheOnly92 schrieb: >> 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. >> >> 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 >> > > As far as i can see, nobody has asked this questions before: if you want to > use memcached > as a session store, how is your setup designed? specialised memcached's > (good, good, good) > or one instance per webserver (bad, bad, bad)? how does your php.ini look > like (all > entries starting with "session")? Do you have a any or even a large number > of evictions on > your memcached's? Is your network saturated (using memcached as a session > store produces a > large amount of network traffic, which can lead to connection problems, > which could also > explain your issue). > > Kind regards, > > Jérôme > -- Von meinen Mobilgerät aus gesendet Martin Grotzke http://www.javakaffee.de/blog/
