diff options
| author | Sanju Rakonde <srakonde@redhat.com> | 2018-02-21 12:46:25 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2018-03-28 04:27:18 +0000 |
| commit | a60fc2ddc03134fb23c5ed5c0bcb195e1649416b (patch) | |
| tree | c4f42085b4c6c6761bf4f3d23a24b8821cf292a8 /rpc | |
| parent | 95601229b8318f015a19d7eff89f73853b684a49 (diff) | |
glusterd: handling brick termination in brick-mux
Problem: There's a race between the last glusterfs_handle_terminate()
response sent to glusterd and the kill that happens immediately if the
terminated brick is the last brick.
Solution: When it is a last brick for the brick process, instead of glusterfsd
killing itself, glusterd will kill the process in case of brick multiplexing.
And also changing gf_attach utility accordingly.
Change-Id: I386c19ca592536daa71294a13d9fc89a26d7e8c0
fixes: bz#1545048
BUG: 1545048
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
Diffstat (limited to 'rpc')
0 files changed, 0 insertions, 0 deletions