REVIEW: https://review.gluster.org/20657 (core: Update condition in get_xlator_by_name_or_type) posted (#3) for review on master by MOHIT AGRAWAL
COMMIT: https://review.gluster.org/20657 committed in master by "Atin Mukherjee" <firstname.lastname@example.org> with a commit message- core: Update condition in get_xlator_by_name_or_type
Problem: Sometimes client connection is failed after throwing
error "cleanup flag is set for xlator Try again later".
The situation comes only after get a detach request but
the brick stack is not completely detached and at the same time
the client initiates a connection with brick
Solution: To resolve the same check cleanup_starting flag in get
xlator_by_name_or_type, this function call by server_setvolume
to attach a client with brick.
Signed-off-by: Mohit Agrawal <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-5.0, please open a new bug report.
glusterfs-5.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.