Bug 763696 (GLUSTER-1964) - need a cmd to get process state dumps
Summary: need a cmd to get process state dumps
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1964
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-15 09:37 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Amar Tumballi 2010-10-15 09:37:23 UTC
We need a gluster command itself to collect state dump, instead of current way of issuing SIGUSR1 on a process id. This is more handy.

Comment 1 Amar Tumballi 2011-04-25 09:33:48 UTC
Please update the status of this bug as its been more than 6months since its filed (bug id < 2000)

Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.

Comment 2 Amar Tumballi 2011-08-22 07:33:45 UTC
Please work on this.

Shishir had sent a patch to handle this: http://patches.gluster.com/patch/7039/ but this may not be enough.

What we should have from this feature.

* Enable an CLI option for setting 'statedump' path for given volume. (and the individual brick dump will have brick-path in its log file name, so it should be uniq per volume).

* Enable a CLI command to take the statedump on all the brick processes which are running at the moment (per volume).

* Enhance the above command of taking statedump to consider only few parts of state-dumps. (inode/memory/priv/stack etc).

Let me know if you have any questions on this.


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