Comment #2 on issue 296 by peter.a....@gmail.com: Should SET operation
returned STORED when unix time expiration has already past
http://code.google.com/p/memcached/issues/detail?id=296
Agreed, on both counts.
It was not immediately obvious to me that it was a time skew problem, as it
was working from one client and not from another client. Both SET
operations returned STORED. But that is because I modified their client
implementation to not use "noreply" so as to check what was happening.
I'll file a bug against OpenStack Swift as well, referencing this bug.
So do folks set values using an absolute (unix) time in the past to verify
memcached is functioning? Or perhaps that a key/value pair is storable (not
too big or something)?
Thanks for indulging me here.
