[Bugs] [Bug 1545048] [brick-mux] process termination race while killing glusterfsd on last brick detach

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1545048



--- Comment #7 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19794 committed in master by "Atin
Mukherjee" <amukherj at redhat.com> with a commit message- Revert "glusterd:
handling brick termination in brick-mux"

This reverts commit a60fc2ddc03134fb23c5ed5c0bcb195e1649416b.

This commit was causing multiple tests to time out when brick 
multiplexing is enabled. With further debugging, it's found that even 
though the volume stop transaction is converted into mgmt_v3 to allow
the remote nodes to follow the synctask framework to process the command,
there are other callers of glusterd_brick_stop () which are not synctask
based.
Change-Id: I7aee687abc6bfeaa70c7447031f55ed4ccd64693
updates: bz#1545048

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.