Red Hat Bugzilla – Bug 1314617
Data Tiering:Don't allow a detach-tier commit if detach-tier start has failed to complete
Last modified: 2016-04-19 03:21:07 EDT
RCA: Checking whether the brick is down or not is done for detach tier.
This patch will do it
REVIEW: http://review.gluster.org/13602 (Tier: making detach start fail when brick on hot tier is down) posted (#1) for review on release-3.7 by hari gowtham (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/13602 committed in release-3.7 by Dan Lambright (email@example.com)
Author: hari <firstname.lastname@example.org>
Date: Fri Feb 19 13:43:48 2016 +0530
Tier: making detach start fail when brick on hot tier is down
backport of : http://review.gluster.org/#/c/13474/6
Currently detach tier start happens even when a hot brick is down
this might lead to data loss.
This patch prevents the detach tier start from being executed
successfully if a brick in hot tier is down
>Signed-off-by: hari <email@example.com>
Signed-off-by: hari <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
Tested-by: hari gowtham <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-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.9, please open a new bug report.
glusterfs-3.7.9 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.