Red Hat Bugzilla – Bug 1273726
Fully support data-tiering in 3.7.x, remove out of 'experimental' status
Last modified: 2016-06-16 12:18:09 EDT
+++ This bug was initially created as a clone of Bug #1221957 +++
GlusterFS 3.7.0 has marked data-tiering as an 'experimental' feature. Basic functionality for data-tiering is available, but with many restrictions and known issues.
This bug tracks the improvements made to tiering. Bug reports to improve tiering in the 3.7 release should have 'glusterfs-tiering-supportability' in the 'blocks' field.
--- Additional comment from Niels de Vos on 2015-05-15 08:52:09 EDT ---
--- Additional comment from Niels de Vos on 2015-06-02 04:20:19 EDT ---
The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.
--- Additional comment from Niels de Vos on 2015-06-20 06:08:21 EDT ---
Unfortunately glusterfs-3.7.2 did not contain a code change that was associated with this bug report. This bug is now proposed to be a blocker for glusterfs-3.7.3.
--- Additional comment from Kaushal on 2015-07-30 09:17:47 EDT ---
This bug could not be fixed in time for glusterfs-3.7.3. This is now being tracked for being fixed in glusterfs-3.7.4.
REVIEW: http://review.gluster.org/12407 (Tier/cli: removing warning message for tiering) posted (#1) for review on master by hari gowtham (email@example.com)
COMMIT: http://review.gluster.org/12407 committed in master by Dan Lambright (firstname.lastname@example.org)
Author: hari gowtham <email@example.com>
Date: Wed Oct 21 12:12:09 2015 +0530
Tier/cli: removing warning message for tiering
The warning message for tiering being under experimental staus is removed.
Signed-off-by: hari gowtham <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Reviewed-by: mohammed rafi kc <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: Dan Lambright <email@example.com>
This bug could not be fixed in time for glusterfs-3.7.4 or glusterfs-3.7.5. This is now being tracked for being fixed in glusterfs-3.7.6.
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 , 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.