[Bugs] [Bug 1241054] New: Data Tiering: Rename of file is not heating up the file

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1241054

            Bug ID: 1241054
           Summary: Data Tiering: Rename of file is not heating up the
                    file
           Product: GlusterFS
           Version: mainline
         Component: tiering
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: josferna at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



nchilaka 2015-07-01 07:33:53 EDT

Description of problem:
=========================
When you rename a cold file, the file should get heated up and eventually move
to hot tier. But that is not happening.
This is a case of metadata change which means ideally it should increase the
counter of file to get heated up, but is not happening

Version-Release number of selected component (if applicable):
============================================================
[root at tettnang ~]# gluster --version
glusterfs 3.7.1 built on Jun 28 2015 11:01:14
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
[root at tettnang ~]# rpm -qa|grep gluster
glusterfs-cli-3.7.1-6.el7rhgs.x86_64
glusterfs-client-xlators-3.7.1-6.el7rhgs.x86_64
glusterfs-fuse-3.7.1-6.el7rhgs.x86_64
glusterfs-geo-replication-3.7.1-6.el7rhgs.x86_64
glusterfs-libs-3.7.1-6.el7rhgs.x86_64
glusterfs-api-3.7.1-6.el7rhgs.x86_64
glusterfs-rdma-3.7.1-6.el7rhgs.x86_64
glusterfs-3.7.1-6.el7rhgs.x86_64
glusterfs-debuginfo-3.7.1-6.el7rhgs.x86_64
glusterfs-server-3.7.1-6.el7rhgs.x86_64
[root at tettnang ~]# 




Steps to Reproduce:
===================
1.create a regular volume and start it.
2.set following options
 performance.quick-read: off
performance.io-cache: off

3.Now attach a tier and enable features.ctr-enabled.
4. fuse mount the volume
5. Create a file and check if it is created in hot tier(works as expected)
6.  Now wait for say about 3min by keeping the setup idle.
7. Now the file should have been moved to cold tier(works as expected)
8.Now do a rename of the file

Actual results:
===============
rename passes, but the file doesnt get heated,even though the ctime changes,
which is a metadata change action

Note:
I haven't set promote/demote freq. Which means the default time should be about
120sec
Also, I haven't turned on  features.record-counters or read/write threshold
counters, which means I file should get heated if modified even once.


Logs will be attached



Expected results:


Additional info:

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.