Bug 1279166 - Data Tiering:Metadata changes to a file should not heat/promote the file
Summary: Data Tiering:Metadata changes to a file should not heat/promote the file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1278754
Blocks: 1282315
TreeView+ depends on / blocked
 
Reported: 2015-11-08 10:26 UTC by Joseph Elwin Fernandes
Modified: 2016-06-16 13:43 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of: 1278754
: 1282315 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:43:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2015-11-15 07:24:41 UTC
REVIEW: http://review.gluster.org/12540 (tier/ctr: Providing option to record or ignore metadata heat) posted (#6) for review on master by Joseph Fernandes

Comment 2 Vijay Bellur 2015-11-15 21:48:02 UTC
COMMIT: http://review.gluster.org/12540 committed in master by Dan Lambright (dlambrig) 
------
commit d4aaa00d77d7a10748a1ca9af82265ad9ac42598
Author: Joseph Fernandes <josferna>
Date:   Sun Nov 8 15:33:15 2015 +0530

    tier/ctr: Providing option to record or ignore metadata heat
    
    Currently we heat up a file for both data and metadata write.
    Here we provide a ctr xlator option called "ctr-record-metadata-heat"
    were the admin can decide on recording metadata heat i.e heatup a
    file on metadata writes or not.
    Metadata data operation are
    a. setattr: explicit changing of atime/mtime using utimes,
                changing of posix permissions of the file
    b. rename: Renaming a file,
    c. unlink, link: adding or deleting hardlinks
    d. xattrs: setting or removal of xattrs.
    
    NOTE: atime, mtime and ctime change through writev, readv, truncate, mknod
    and create will not be considered here as these fops are data and primary
    metadata fops.
    
    Defaultly "ctr-record-metadata-heat" is off. Admin can
    switch it on using gluster volume set command.
    
    Change-Id: I91157509255dd5cb429cda2b6d4f64582e155e7b
    BUG: 1279166
    Signed-off-by: Joseph Fernandes <josferna>
    Reviewed-on: http://review.gluster.org/12540
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Niels de Vos 2016-06-16 13:43:12 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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