diff options
| author | Sanju Rakonde <srakonde@redhat.com> | 2018-04-06 01:53:45 +0530 |
|---|---|---|
| committer | Amar Tumballi <amarts@redhat.com> | 2018-05-07 15:31:59 +0000 |
| commit | 4da244caccd38a77de5428b6954f565219ef0719 (patch) | |
| tree | 43311ffe448d78206aa4f68b1be07d2c38ac4bc3 /extras/LinuxRPM | |
| parent | 23c1385b5f6f6103e820d15ecfe1df31940fdb45 (diff) | |
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@redhat.com>
Diffstat (limited to 'extras/LinuxRPM')
0 files changed, 0 insertions, 0 deletions