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.
*** Bug 905747 has been marked as a duplicate of this bug. ***
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.
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.
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.
http://review.gluster.org/12407
REVIEW: http://review.gluster.org/12412 (Tier/cli: removing warning message for tiering) posted (#1) for review on release-3.7 by hari gowtham (hari.gowtham005)
COMMIT: http://review.gluster.org/12412 committed in release-3.7 by Dan Lambright (dlambrig) ------ commit 89a68feb5261de2238e7a23fece74e2f19220334 Author: hari gowtham <hgowtham> Date: Wed Oct 21 12:12:09 2015 +0530 Tier/cli: removing warning message for tiering back-port of :http://review.gluster.org/#/c/12407/ The warning message for tiering being under experimental staus is removed. >Change-Id: I7d1d535d380b672c70f03ecc0d24a113600ea43f >BUG: 1273726 >Signed-off-by: hari gowtham <hgowtham> >Reviewed-on: http://review.gluster.org/12407 >Tested-by: NetBSD Build System <jenkins.org> >Reviewed-by: mohammed rafi kc <rkavunga> >Tested-by: Gluster Build System <jenkins.com> >Reviewed-by: Dan Lambright <dlambrig> >Tested-by: Dan Lambright <dlambrig> Change-Id: I957c4fd557908586183fefadd448b76391b4911a BUG: 1221957 Signed-off-by: Hari Gowtham <hgowtham> Reviewed-on: http://review.gluster.org/12412 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig>
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.7.6, please open a new bug report. glusterfs-3.7.6 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://www.gluster.org/pipermail/gluster-users/2015-November/024359.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user