Description of problem: Currently interval stats are cleared upon "volume profile info" automatically and there isn't a command to clear cumulative stats. This ticket is a follow up to Anand's comment in http://review.gluster.org/#/c/6264/. i.e. "... implement 'volume profile peek' and 'volume profile clear' commands - where peek will not wipe the interval stats and clear will wipe both interval and cumulative stats" Version-Release number of selected component (if applicable): How reproducible: Feature does not exist. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I am working on a patch for this.
REVIEW: http://review.gluster.org/6620 (cli: Add options to the CLI that let the user control the reset of stats) posted (#1) for review on master by Dawit Alemu (dalemu)
REVIEW: http://review.gluster.org/6620 (cli: Add options to the CLI that let the user control the reset of stats) posted (#2) for review on master by Dawit Alemu (dalemu)
REVIEW: http://review.gluster.org/6620 (cli: Add options to the CLI that let the user control the reset of stats) posted (#3) for review on master by Dawit Alemu (dalemu)
COMMIT: http://review.gluster.org/6620 committed in master by Vijay Bellur (vbellur) ------ commit 48b8186bdc2f5e45b58aadf849b2bd60c9a77330 Author: Dawit Alemu <dalemu> Date: Mon Dec 30 22:59:39 2013 -0500 cli: Add options to the CLI that let the user control the reset of stats "volume profile info" automatically clears incremental stats. There isn't a command to: - fetch stats without clearing incremental stats and - clear cumulative and incremental stats This change introduces two arguments (i.e. peek and clear). 'clear' will wipe both incremental and cumulative stats. 'peek' fetches stats without wiping incremental stats. 'volume profile info peek' - fetches incremental and cumulative stats without wiping incremental stats 'volume profile info incremental peek' - fetches incremental stats without wiping incremental stats 'volume profile info clear' - clears both incremental and cumultiave stats Change-Id: I91834515ad672eca5f882809941147d7d997c4c9 BUG: 1047416 Signed-off-by: Dawit Alemu <dalemu> Reviewed-on: http://review.gluster.org/6620 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> Reviewed-by: Vijay Bellur <vbellur>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users