Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 342 by [email protected]: Age value being reset when key being
requested if age over 60.
http://code.google.com/p/memcached/issues/detail?id=342
What steps will reproduce the problem?
1. Run memcached with -vv
2. Monitor the log for the {s,g}et of a specific key.
3. Regularly, (say every 5 - 10 sec) run a request for the monitored key.
4. Run a watch statement on memcached-tool display, monitoring the age of
the key.
What is the expected output? What do you see instead?
I expect the age value to keep growing until the key gets set.
I see the age being reset to 0 at the first get request after 60 seconds,
despite no set being logged in either my application, nor memcached's log.
What version of the product are you using? On what operating system?
1.4.5. CentOS 5.9.
Please provide any additional information below.
Normally my application would not set and expiry in memcached, but instead
manage it's own expire value as a part of the value, so I expect the value
to be kept around "forever". As far as I can tell, that's what happens, but
the age value indicates otherwise.
If I set an expire of 90 seconds, I see the age tick up to 60, reset to 0,
tick up to 30, set request comes in, so the age resets again, and then the
process repeats.
I've done what I can to reasonably rule this out as an error in my
application, but it's obviously entirely possible that I'm missing
something.
Kind regards, Claes
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
