Bug 1252851 - [CACHE-TIER]: object not evicted from the cache pool based on target_max_object policy
Summary: [CACHE-TIER]: object not evicted from the cache pool based on target_max_obje...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 1.3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 1.3.2
Assignee: Loic Dachary
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-12 11:24 UTC by shylesh
Modified: 2017-07-30 15:13 UTC (History)
6 users (show)

Fixed In Version: RHEL: ceph-0.94.5-1.el7cp Ubuntu: ceph_0.94.5-2redhat1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-29 14:42:54 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 12673 0 None None None Never
Red Hat Product Errata RHBA-2016:0313 0 normal SHIPPED_LIVE Red Hat Ceph Storage 1.3.2 bug fix and enhancement update 2016-02-29 19:37:43 UTC

Description shylesh 2015-08-12 11:24:23 UTC
Description of problem:
tiering agent is not evicting the objects based on target_max_objects policy

Version-Release number of selected component (if applicable):
0.94.1.4-1trusty

How reproducible:
always

Steps to Reproduce:
 
 http://tracker.ceph.com/issues/12673#change-56512
 

Actual results:


Expected results:


Additional info:

Comment 2 Kefu Chai 2015-08-13 05:48:59 UTC
see the http://tracker.ceph.com/issues/12673#note-9 , it's expected behaviour.

Comment 3 Kefu Chai 2015-08-13 08:50:04 UTC
i am still on it.

Comment 4 Ken Dreyer (Red Hat) 2015-12-11 21:52:10 UTC
https://github.com/ceph/ceph/pull/5765 merged upstream and shipped in upstream's v0.94.4. This will be in RHCS 1.3.2.

Comment 6 shylesh 2016-02-06 17:26:21 UTC
Verified on ceph-0.94.5-4.el7cp.x86_64

Now the objects which are promoted and evicted based on target_max_object policy.
Though always cache pool makes sure that number of objects < target_max_object but exact number of target_max_object limit is not satisfied for which I will log a new bug https://bugzilla.redhat.com/show_bug.cgi?id=1305283.

Comment 8 errata-xmlrpc 2016-02-29 14:42:54 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/RHBA-2016:0313


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