diff options
author | Mohit Agrawal <moagrawal@redhat.com> | 2019-04-05 09:46:24 +0530 |
---|---|---|
committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2019-04-08 14:02:26 +0000 |
commit | e26fc565990091ac18acd2859296029d3b7609b4 (patch) | |
tree | 1e565c68c2b1b5cfe9d8605a6c16c0ebad67e08d /xlators/performance/write-behind/src/write-behind.c | |
parent | 3f9f00b2e5ec4ad845f3c8edef56fec0b4e4bbc1 (diff) | |
download | glusterfs-e26fc565990091ac18acd2859296029d3b7609b4.tar.gz glusterfs-e26fc565990091ac18acd2859296029d3b7609b4.tar.xz glusterfs-e26fc565990091ac18acd2859296029d3b7609b4.zip |
glusterfsd: Multiple shd processes are spawned on brick_mux environment
Problem: Multiple shd processes are spawned while starting volumes
in the loop on brick_mux environment.glusterd spawn a process
based on a pidfile and shd daemon is taking some time to
update pid in pidfile due to that glusterd is not able to
get shd pid
Solution: Commit cd249f4cb783f8d79e79468c455732669e835a4f changed
the code to update pidfile in parent for any gluster daemon
after getting the status of forking child in parent.To resolve
the same correct the condition update pidfile in parent only
for glusterd and for rest of the daemon pidfile is updated in
child
> Change-Id: Ifd14797fa949562594a285ec82d58384ad717e81
> fixes: bz#1684404
> Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
> (Cherry picked from commit 66986594a9023c49e61b32769b7e6b260b600626)
> (Reviewed on upstream link https://review.gluster.org/#/c/glusterfs/+/22290/)
Change-Id: Ie295e905c01f2749bc39da5511537cc9a85832e5
fixes: bz#1696513
Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
Diffstat (limited to 'xlators/performance/write-behind/src/write-behind.c')
0 files changed, 0 insertions, 0 deletions