On 12 Okt., 18:52, dormando <[email protected]> wrote: > > The Dev server has this issue: > > - items that are not yet expired (I had a sample with 35 minutes > > lifetime left) get removed from the cache > > - the memcache has plenty of free memory from the default 64MB > > - the server has 12GB of free memory > > > Any good reason why a valid item is removed with plenty of free space? > > Your clock is probably drifting. Try 1.4.7 or newer?
The general problem with "trying a newer version" is that we'd prefer to use the OS's packaging mechanisms. So those are the latest versions available. Also there might be many dependency problems and such. For sure, we want properly working Memcaches in the first place. ;-) Is there any way to find out if our clock is really drifting? I could not see any timestamp that looked wrong anywhere. Also we're not talking about 3 seconds but up to minutes to ealy expiry! > > The Live server has a more severe issue: > > - items that ARE expired are returned > > - if I log into memcached via telnet and issue a flush_all command the > > items are gone; this makes no sense to me as flush_all does only > > expire > > items, lazy remove is purging them > > The 1.4.2 ubuntu guy has bugs with multigets (and probably something > else...). Not sure I understand what you mean by "all the items are gone" > - that's sort of what flush_all does, albeit lazily. What exactly are you > looking at when you say this? Sure, flush_all should do that. But also expired items should be removed. So I was wondering why items that I see as expired don't get nuked, but then still the "flush_all" can do the job right! Clock drifting: We're talking about many hours here. Expired items just never get nuked by expiry! Is there any trustworthy source of .deb packages for Memcached where we could pull a current version? Best regards, Anton
