Red Hat Bugzilla – Bug 1282315
Data Tiering:Metadata changes to a file should not heat/promote the file
Last modified: 2016-04-19 03:48:11 EDT
REVIEW: http://review.gluster.org/12582 (tier/ctr: Providing option to record or ignore metadata heat) posted (#1) for review on release-3.7 by Joseph Fernandes
COMMIT: http://review.gluster.org/12582 committed in release-3.7 by Dan Lambright (firstname.lastname@example.org)
Author: Joseph Fernandes <email@example.com>
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
Defaultly "ctr-record-metadata-heat" is off. Admin can
switch it on using gluster volume set command.
Backport of http://review.gluster.org/12540
> Change-Id: I91157509255dd5cb429cda2b6d4f64582e155e7b
> BUG: 1279166
> Signed-off-by: Joseph Fernandes <firstname.lastname@example.org>
> Reviewed-on: http://review.gluster.org/12540
> Tested-by: NetBSD Build System <email@example.com>
> Tested-by: Gluster Build System <firstname.lastname@example.org>
> Reviewed-by: Dan Lambright <email@example.com>
> Tested-by: Dan Lambright <firstname.lastname@example.org>
Signed-off-by: Joseph Fernandes <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Reviewed-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: Dan Lambright <email@example.com>
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.7.7, please open a new bug report.
glusterfs-3.7.7 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.