Bug 1493422 - AFR : [RFE] Improvements needed in "gluster volume heal info" commands
Summary: AFR : [RFE] Improvements needed in "gluster volume heal info" commands
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: 3.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Karthik U S
QA Contact:
URL:
Whiteboard:
Depends On: 1261463
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-20 07:38 UTC by Karthik U S
Modified: 2018-10-23 13:52 UTC (History)
8 users (show)

Fixed In Version:
Clone Of: 1261463
Environment:
Last Closed: 2018-10-23 13:52:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Karthik U S 2017-09-20 07:39:56 UTC
Description of problem:
========================
To know whether there are any pending self-heals on the volume we use "gluster volume heal <volume_name> info" command. This will print "Number of Entries" per brick as well as filenames/GFID's of the files to be self-healed. 

Sometimes one might just need to know how many self-heals are pending on the volume rather than knowing each and every files filename/GFID. (If there are millions of files to be self-healed knowing each and every filename would be meaningless). 

At the same time whenever a user need to know what files needs self-heals then we should be able to provide that information as well. One of the case can be self-heal is taking a very long time and user wants to see on what files self-heal is pending. 

Hence, It will be really informative if we can separate this one command "gluster volume heal <volume_name> info" into two different commands for : 

1) command which gives summary of number of pending entries

2) command which details on what files needs self-heal

Comment 2 Worker Ant 2017-09-20 07:51:22 UTC
REVIEW: https://review.gluster.org/18327 (heal: New feature heal info summary to list the status of brick and count of entries to be healed) posted (#1) for review on release-3.12 by Karthik U S (ksubrahm)

Comment 3 Shyamsundar 2018-10-23 13:52:09 UTC
The work is deemed a feature and is present in the future releases, and is not backported to this release. This bug is hence closed appropriately.


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