REVIEW: https://review.gluster.org/21743 (glusterd: don't acquire locks on resources when cleanup is already started) posted (#1) for review on master by Sanju Rakonde
REVIEW: https://review.gluster.org/21743 (glusterd: perform rcu_read_lock/unlock() under cleanup_lock mutex) posted (#5) for review on master by Atin Mukherjee
REVIEW: https://review.gluster.org/21974 (glusterd: kill the process without releasing the cleanup mutex lock) posted (#1) for review on master by Sanju Rakonde
REVIEW: https://review.gluster.org/22146 (glusterd: adding a comment for code readability) merged (#5) on master by Atin Mukherjee
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-6.0, please open a new bug report.
glusterfs-6.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.