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.
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.
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.