Bug 1319017 - Better logging of self heal operations
Summary: Better logging of self heal operations
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: replicate
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Pranith Kumar K
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 12:39 UTC by Tupper Cole
Modified: 2018-04-16 18:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-16 18:15:38 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tupper Cole 2016-03-18 12:39:56 UTC 
Description of problem:
There is no current method to look at the status of a self heal operation other than `gluster volume <volume> heal info` which lists heals that may be occurring. Logging to /var/log/glusterfs/glustershd.log only notes the time when a heal is complete. A status (%, number of files, etc) would be helpful in monitoring self heal.
Note You need to log in before you can comment on or make changes to this bug.