Bug 1785143 - Multiple glusterfsd process spawn when glusterd restart during a volume start.
Summary: Multiple glusterfsd process spawn when glusterd restart during a volume start.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-19 09:23 UTC by Mohammed Rafi KC
Modified: 2020-02-24 10:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-02-24 10:59:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23906 0 None Open mgmt/brick-mux: Avoid sending two response when attach is failed. 2019-12-31 13:35:41 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.