Bug 1584829

Summary: objects in cache never refresh after rgw_cache_expiry_interval
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Justin Bautista <jbautist>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: Tejas <tchandra>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: unspecified    
Version: 2.5CC: agunn, cbodley, ceph-eng-bugs, federico, hnallurv, kbader, mbenjamin, mhackett, owasserm, sweil, tchandra, tserlin
Target Milestone: z1   
Target Release: 2.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHEL: ceph-10.2.10-22.el7cp Ubuntu: ceph_10.2.10-19redhat1 Doc Type: Bug Fix
Doc Text:
.Cache entries were not refreshing as expected The new time-based metadata cache entry expiration logic did not include logic to update the expiration time on already-cached entries being updated in place. Cache entries became permanently stale after expiration, leading to a performance regression as metadata objects were effectively not cached and always read from the cluster. Logic was added to update the expiration time of cached entries when updated.
 Story Points: ---
Clone Of:
: 1585748 1585750 (view as bug list) Environment:
Last Closed: 2018-07-26 18:06:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1536401, 1585748, 1585750    

Description Justin Bautista 2018-05-31 18:04:21 UTC 
Creating BZ based on upstream pull request/tracker: 
https://github.com/ceph/ceph/pull/22324

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
Comment 21 errata-xmlrpc 2018-07-26 18:06:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2261