Description of problem:
Currently upon peer detach glusterd stopping all the daemon's of existing volume.
Upon peer detach it should not stop all the daemon's of existing volume
REVIEW: http://review.gluster.org/12838 (glusterd: stop daemon services upon peer detach correctly) posted (#2) for review on master by Gaurav Kumar Garg (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/12838 (glusterd: stop daemon services upon peer detach correctly) posted (#3) for review on master by Gaurav Kumar Garg (email@example.com)
COMMIT: http://review.gluster.org/12838 committed in master by Atin Mukherjee (firstname.lastname@example.org)
Author: Gaurav Kumar Garg <email@example.com>
Date: Tue Dec 1 19:14:08 2015 +0530
glusterd: stop daemon services upon peer detach correctly
Currently glusterd is stopping all the daemons service upon peer detach.
If user have multi node cluster and if user want to detach any node
from the cluster, and detached node having stand alone volume then upon
detaching glusterd stopping all the daemon's of the detached node,
which is having running volume.
Upon peer detach it should do peer detach cleanup properly and it should
stop only those daemon on the node on which it require.
Signed-off-by: Gaurav Kumar Garg <firstname.lastname@example.org>
Reviewed-by: Atin Mukherjee <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <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.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.