Bug 1414273 - [RFE] Enhance volume statedump command to include glusterd's statedump support
Summary: [RFE] Enhance volume statedump command to include glusterd's statedump support
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-18 08:49 UTC by Samikshan Bairagya
Modified: 2018-11-19 05:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:19:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 580 0 None None None 2018-11-19 05:27:52 UTC
Red Hat Bugzilla 1169302 0 unspecified CLOSED Unable to take Statedump for gfapi applications 2021-02-22 00:41:40 UTC

Internal Links: 1169302

Description Samikshan Bairagya 2017-01-18 08:49:21 UTC
Description of problem: 

Currently to get the statedump for glusterd, the user needs to send a SIGUSR1 to the glusterd process. This generates a statedump for glusterd in /var/run/gluster/. The volume statedump CLI can already generate statedumps for bricks, nfs server, and quotad. However, many users use this command to get statedump for glusterd, but instead end up taking statedump for brick processes, as they are more familiar with this command. It would be nice if this command could support statedump for glusterd too.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Vijay Bellur 2018-11-19 05:27:52 UTC
Migrated to github:

https://github.com/gluster/glusterfs/issues/580

Please follow the github issue for further updates on this bug.


Note You need to log in before you can comment on or make changes to this bug.