[Bugs] [Bug 1698131] multiple glusterfsd processes being launched for the same brick, causing transport endpoint not connected

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1698131

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
             Blocks|                            |1692394 (glusterfs-6.1)
              Flags|                            |needinfo?(budic at onholygroun
                   |                            |d.com)



--- Comment #2 from Atin Mukherjee <amukherj at redhat.com> ---
Two requests I have from you:

1. Could you pass back the output of 'gluster peer status' and 'gluster volume
status'
2. Could you share the tar of /var/log/glusterfs/*.log ? 


Please note that we did fix a similar problem in glusterfs-6.0 with the
following commit, but if you're still able to reproduce it we need to
investigate. On a test setup, running a volume start and ps aux | grep
glusterfsd only shows me the required brick processes though, but the details
asked for might give us more insights.

commit 36c75523c1f0545f32db4b807623a8f94df98ca7
Author: Mohit Agrawal <moagrawal at redhat.com>
Date:   Fri Mar 1 13:41:24 2019 +0530

    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 at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1692394
[Bug 1692394] GlusterFS 6.1 tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.