[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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #9 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19829 committed in master by "Amar Tumballi"
<amarts at redhat.com> with a commit message- glusterd: handling brick termination
in brick-mux

Problem: There's a race between the glusterfs_handle_terminate()
response sent to glusterd from last brick of the process and the
socket disconnect event that encounters after the brick process
got killed.

Solution: When it is a last brick for the brick process, instead of
sending GLUSTERD_BRICK_TERMINATE to brick process, glusterd will
kill the process (same as we do it in case of non brick multiplecing).

The test case is added for https://bugzilla.redhat.com/show_bug.cgi?id=1549996

Change-Id: If94958cd7649ea48d09d6af7803a0f9437a85503
fixes: bz#1545048
Signed-off-by: Sanju Rakonde <srakonde at redhat.com>

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