swift.common.memcached client always uses absolute (unix) time expiration values
Bug #1076148 reported by
Peter Portante
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Peter Portante |
Bug Description
The current memcached client implementation always uses absolute (unix) time values when a time is provided. This requires that the client server time and the memcached server time are in sync.
Seems like using delta timeout values will work just fine, and prevent unexpected behaviors in how objects are cached when server times are not in sync. See http://
Changed in swift: | |
milestone: | none → 1.7.6 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
There's a bunch of other things that break when the times on your cluster nodes get out of sync, so some kind of time synchronizer is essential.
I guess you could have a separate set of memcached boxes whose time could drift, though.