We've updated memcached to the most recent version. So far the issue did not rise again.
Thanks for your help On Jun 19, 2:06 pm, Sebastian <[email protected]> wrote: > Hello, > > Memcached is currently on the same server than apache. > > Cheers, > > Sebastian > > On 19 Jun., 14:01, Adam Allgaier <[email protected]> wrote: > > > We've experienced a similar issue when server times were not synchronized > > between the web and memcached server (our client sets the expiry based on > > the web server time, not the memcached server time) > > > Adam > > > ----- Original Message ---- > > From: Sebastian <[email protected]> > > To: memcached <[email protected]> > > Sent: Friday, June 19, 2009 2:29:16 AM > > Subject: Sporadically cache entries do not expire > > > Dear all, > > > Now for the third time we have noticed an unusual behaviour resulting > > in getting back cache hits, which should have been expired. All of our > > keys have a maximum lifecycle of 5 minutes. But again since yesterday > > evening it seems that all keys are still in the cache, also they have > > been set with an expiry time of 60 - 300 seconds. > > Once we flush all the keys or we restart memcached, everything is > > working as intended again. > > > But from time to time it seems that the expiry time gets ignored, > > resulting in getting old keys back. From what i can see, all keys are > > affected then. > > > As mentioned above, after a restart/flush everything is fine, but > > after a few days the issue rises again. Maybe someone has an idea what > > could result in such behaviour? > > > Thank you for your help, > > > Sebastian
