Bug 1584829 - objects in cache never refresh after rgw_cache_expiry_interval
Summary: objects in cache never refresh after rgw_cache_expiry_interval
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW
Version: 2.5
Hardware: x86_64
OS: Linux
Target Milestone: z1
: 2.5
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
Aron Gunn
Depends On:
Blocks: 1536401 1585748 1585750
TreeView+ depends on / blocked
Reported: 2018-05-31 18:04 UTC by Justin Bautista
Modified: 2018-07-26 18:08 UTC (History)
12 users (show)

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.
Clone Of:
: 1585748 1585750 (view as bug list)
Last Closed: 2018-07-26 18:06:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2261 None None None 2018-07-26 18:08:06 UTC
Ceph Project Bug Tracker 24346 None None None 2018-05-31 18:04:20 UTC

Description Justin Bautista 2018-05-31 18:04:21 UTC
Creating BZ based on upstream pull request/tracker: 

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.


Note You need to log in before you can comment on or make changes to this bug.