Bug #24346
closed
objects in cache never refresh after rgw_cache_expiry_interval
Added by Casey Bodley almost 6 years ago.
Updated over 4 years ago.
Backport:
luminous mimic jewel
Description
ObjectCacheInfo::time_added is only initialized on first insert. so once an entry reaches its rgw_cache_expiry_interval, it can't be refreshed until the lru removes its entry entirely
I'm unclear why there is any trace of already-expired items. I guess the intrusive cache change doesn't have this issue?
- Status changed from 12 to Fix Under Review
Matt Benjamin wrote:
I'm unclear why there is any trace of already-expired items. I guess the intrusive cache change doesn't have this issue?
ObjectCache::get() only takes a read lock, so does not remove these expired items from the map. the lru will remove them eventually
- Status changed from Fix Under Review to Pending Backport
- Backport changed from luminous mimic to luminous mimic jewel
jewel added to backports list as the cache expiration change is present
It would be great if this can make it to Jewel 10.2.11, thanks!
- Copied to Backport #24384: luminous: objects in cache never refresh after rgw_cache_expiry_interval added
- Copied to Backport #24385: mimic: objects in cache never refresh after rgw_cache_expiry_interval added
- Copied to Backport #24386: jewel: rgw: objects in cache never refresh after rgw_cache_expiry_interval added
Pavan Rallabhandi wrote:
It would be great if this can make it to Jewel 10.2.11, thanks!
Do you want to take #24386 then? If you stage the backport quickly, it might make it in.
Nathan Cutler wrote:
Pavan Rallabhandi wrote:
It would be great if this can make it to Jewel 10.2.11, thanks!
Do you want to take #24386 then? If you stage the backport quickly, it might make it in.
Sorry Nathan, somehow missed this update. Have raised a backport PR for Jewel now, hope this is still in time.
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF