Bug 1286654 - Data Tiering:Read heat not getting calculated and read operations not heating the file with counter enabled
Summary: Data Tiering:Read heat not getting calculated and read operations not heating...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: tier
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: RHGS 3.1.2
Assignee: Joseph Elwin Fernandes
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On:
Blocks: 1260783 1286656 1287583
TreeView+ depends on / blocked
 
Reported: 2015-11-30 12:16 UTC by Nag Pavan Chilakam
Modified: 2019-04-03 09:15 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.7.5-9
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1286656 (view as bug list)
Environment:
Last Closed: 2016-03-01 05:59:52 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0193 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 update 2 2016-03-01 10:20:36 UTC

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
Note You need to log in before you can comment on or make changes to this bug.