Question

We have found that with our memcache some keys tend to be lost. To debug, I am using the command stats cachedump <slab> <limit>

The output is something like this :

ITEM key-stuff-123-mlgtr-tmura [58 b; 1256946310 s]
ITEM key-stuff-123-mlgtr-isuca [58 b; 1256946310 s]
ITEM key-stuff-123-mlgtr-arpan [58 b; 1256946310 s]
ITEM key-stuff-123-mlgtr-nanhai [59 b; 1256946252 s]
ITEM key-stuff-123-mlgtr-naka3 [58 b; 1256946250 s]
ITEM key-stuff-123-mlgtr-erlang [59 b; 1256946250 s]
ITEM key-stuff-123-mlgtr-junkma [59 b; 1256946250 s]
ITEM key-stuff-123-mlgtr-wilfue [59 b; 1256946250 s]
ITEM key-stuff-123-mlgtr-quinte [59 b; 1256946250 s]
ITEM key-stuff-123-mlgtr-yanbe [58 b; 1256946250 s]

I get that 58 b is the size; but what would be 1256946250 s? The expiration in seconds? That seems kind of high (55 years)! So maybe our problem lies here… or maybe I misunderstood something.

Thanks!

Answer 1

It’s the expiration time, as a unix timestamp.

So, item with ‘1256946250’ will expire ‘Sat Oct 31 01:44:10 2009’