Comment #5 on issue 389 by [email protected]: internal clock drift from
system time
https://code.google.com/p/memcached/issues/detail?id=389
D*mn, I wrote this bug report under wrong assumptions. I've now realized
what the real bug is and of course it's in the proprietary software that
we're using.
It's wrongly sending absolute time stamps in one specific case where only a
short relative value of 30s must be used (i.e. well below the 2592000s or
30 days limit). Initially spotting that memcached and the system time were
skewed between 5 and 10 minutes on all of our machines set me on a wrong
track from the beginning and I somehow missed the importance of relative
vs. absolute.
It really only affects the few users that need time spans >30d, which we do
not at this time, and the impact is a lot less then. Sorry for the
inconvenience.
--
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/d/optout.
