Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1785143

Summary: Multiple glusterfsd process spawn when glusterd restart during a volume start.
Product: [Community] GlusterFS Reporter: Mohammed Rafi KC <rkavunga>
Component: glusterdAssignee: Mohammed Rafi KC <rkavunga>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, srakonde
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-24 10:59:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mohammed Rafi KC 2019-12-19 09:23:55 UTC
Description of problem:
Multiple glusterfsd process spawn when glusterd restart during a volume start.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a 3 node cluster.
2. Set cluster.brick-multiplex to enable.
3. Create 15 volumes of type replica 1x3. 
4. Start all the volumes one by one.
5. While the volumes are starting reboot one node.

Actual results:
Multiple brick processes are observed.

Expected results:
Single brick process should be observed.

Additional info:

Comment 1 Worker Ant 2019-12-19 09:28:31 UTC
REVIEW: https://review.gluster.org/23906 (mgmt/brick-mux: Avoid sending two response when attach is failed.) posted (#2) for review on master by mohammed rafi  kc

Comment 2 Worker Ant 2019-12-31 13:35:42 UTC
REVIEW: https://review.gluster.org/23906 (mgmt/brick-mux: Avoid sending two response when attach is failed.) merged (#4) on master by MOHIT AGRAWAL

Comment 3 Sanju 2020-02-04 08:50:13 UTC
Not sure why the bot didn't close the bug although the patch is merged.

Comment 4 Sanju 2020-02-04 08:53:13 UTC
I understood it now, the commit says, it updates the bug not fixes. Re-opening the bug.

Comment 5 Sanju 2020-02-24 10:59:04 UTC
https://review.gluster.org/#/c/glusterfs/+/23724/ fixed it, closing the bug.