Red Hat Bugzilla – Bug 1293698
[Tier]: start tier daemon using rebal tier start doesnt start tierd if it is failed on any of single node
Last modified: 2016-04-19 03:51:49 EDT
REVIEW: http://review.gluster.org/13069 (Tier: "tier start force" command implementation) posted (#1) for review on release-3.7 by hari gowtham (email@example.com)
COMMIT: http://review.gluster.org/13069 committed in release-3.7 by Dan Lambright (firstname.lastname@example.org)
Author: hari gowtham <email@example.com>
Date: Wed Dec 16 16:18:29 2015 +0530
Tier: "tier start force" command implementation
back port of : http://review.gluster.org/#/c/12983/
The start command doesnt restart the tier deamon if the deamon
is running at one node. hence to bring up the tierd on the nodes
where the deamon is down, the force command is implemented.
It skips the check for tierd running.
>Signed-off-by: hari gowtham <firstname.lastname@example.org>
Signed-off-by: hari <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>
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.