diff options
| author | Mohit Agrawal <moagrawa@redhat.com> | 2017-06-22 16:57:04 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2017-06-27 10:57:55 +0000 |
| commit | b71059960f8c67d9a058244d2a1c748be4fe1323 (patch) | |
| tree | 78c0ee3b75c543fc0548d8ecf2d29b21939e89b7 /libglusterfs | |
| parent | 4700c5be55b0e567755b4c8a1a91f33d29c06e6b (diff) | |
glusterd: brick process fails to restart after gluster pod failure
Problem: In container environment sometime after delete gluster pod
and created new gluster pod brick process doesn't seem
to come up.
Solution: On the basis of logs it seems glusterd is trying to attach
with non glusterfs process.Change the code of function
glusterd_get_sock_from_brick_pid to fetch socketpath from argument
of running brick process.
BUG: 1464072
Change-Id: Ida6af00066341b683bbb4440d7a0d8042581656a
Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Reviewed-on: https://review.gluster.org/17601
Smoke: Gluster Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Diffstat (limited to 'libglusterfs')
0 files changed, 0 insertions, 0 deletions