summaryrefslogtreecommitdiffstats
path: root/doc/release-notes/6.0.md
diff options
context:
space:
mode:
authorMohit Agrawal <moagrawal@redhat.com>2019-03-01 13:41:24 +0530
committerShyamsundar Ranganathan <srangana@redhat.com>2019-03-12 20:52:59 +0000
commit36c75523c1f0545f32db4b807623a8f94df98ca7 (patch)
tree9cf152a85381e38400da01094213c34d07443f17 /doc/release-notes/6.0.md
parent9b58cfc83c26aa09eb1de8187cc65ed0c3390e97 (diff)
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 > (Cherry pick from commit 66986594a9023c49e61b32769b7e6b260b600626) > (Reviewed on upstream link https://review.gluster.org/#/c/glusterfs/+/22290/) Change-Id: I9a68064d2da1acd0ec54b4071a9995ece0c3320c fixes: bz#1683880 Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
Diffstat (limited to 'doc/release-notes/6.0.md')
0 files changed, 0 insertions, 0 deletions