Bug 1286654

Summary: Data Tiering:Read heat not getting calculated and read operations not heating the file with counter enabled
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: tierAssignee: Joseph Elwin Fernandes <josferna>
Status: CLOSED ERRATA QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: dlambrig, josferna, kramdoss, rcyriac, rhs-bugs, sankarshan, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.5-9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1286656 (view as bug list) Environment:
Last Closed: 2016-03-01 05:59:52 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: 1260783, 1286656, 1287583    

Description Nag Pavan Chilakam 2015-11-30 12:16:17 UTC
Description of problem:
======================
read operations are not heating files when counters are enabled


Version-Release number of selected component (if applicable):
================================
3.7.5-7

Comment 3 krishnaram Karthick 2015-12-16 08:31:32 UTC
Verified the fix on build glusterfs-3.7.5-11.el7rhgs.x86_64.

Tests done to verify:

Test1: 
1) Attached a hot tier to an existing volume with data
2) Did a 'cat' on one of the existing files --> File got promoted

Test2: 
1) Attached a hot tier to an existing volume with data
2) copied files(which were in cold-tier) from client to a different host -> Files got promoted

Comment 5 errata-xmlrpc 2016-03-01 05:59:52 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://rhn.redhat.com/errata/RHBA-2016-0193.html