Memcache cachedump statistics

Question

We found that with our memcache, some keys are usually lost. For debugging, I use the commandstats cachedump <slab> <limit>

The result looks 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 bis size; but what will happen 1256946250 s? Expiration in seconds? It seems tall (55 years old)! So maybe our problem is here ... or maybe I didn’t understand something.

Thanks!

Answer 1

This expiration time is like a unix timestamp.

So, the element with '1256946250' will expire 'Sat 31 Oct 01:44:10 2009'

Answer 2

unix. , . , 01 1970 .