[Bugs] [Bug 1614124] glusterfsd process crashed in a multiplexed configuration during cleanup of a single brick-graph triggered by volume-stop.

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 10 17:48:45 UTC 2018


Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
             Status|POST                        |MODIFIED

--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/20657 committed in master by "Atin
Mukherjee" <amukherj at redhat.com> 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.

Change-Id: I3720e42642fe495dd05211e2ed2cb976db9e231b
fixes: bz#1614124
Signed-off-by: Mohit Agrawal <moagrawal at redhat.com>

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Vc3tw3BiQp&a=cc_unsubscribe

More information about the Bugs mailing list