Bug 1880109

Summary: [RFE] Need a quick , reliable list of files in healing
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Andrew Robinson <anrobins>
Component: disperseAssignee: Ashish Pandey <aspandey>
Status: CLOSED DUPLICATE QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: aspandey, ravishankar, rhs-bugs, sajmoham, storage-qa-internal
Target Milestone: ---Keywords: RFE
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.5.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-24 11:34:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Robinson 2020-09-17 17:19:52 UTC 
Before you record your issue, ensure you are using the latest version of Gluster.

Yes

Provide version-Release number of selected component (if applicable):

RHGS 3.5
 
Have you searched the Bugzilla archives for same/similar issues reported.

Yes
 
Have you discovered any workarounds?. If not, Read the troubleshooting documentation to help solve your issue. ( https://mojo.redhat.com/groups/gss-gluster (Gluster feature and its troubleshooting)  https://access.redhat.com/articles/1365073 (Specific debug data that needs to be collected for GlusterFS to help troubleshooting)

No


Describe the issue:(please be detailed as possible and provide log snippets)
[Provide TimeStamp when the issue is seen]

For gluster support, we need a command that will reliably and quickly give us a list of the files in healing. 

Many times, the 'gluster volume heal <vol> info' command hangs at some point. This tends to happen when healing is the critical problem for the gluster cluster. Sometimes the command will complete after many hours. Sometimes the command does not complete at all. At the least, this slows down the troubleshooting and remediation. At the worst, this brings the troubleshooting process to a complete halt.


Is this issue reproducible? If yes, share more details.:

The long delay in the 'gluster volume heal <vol> info' command tends to happen when there is a very high number of files in healing or when the gluster node is very busy.

Steps to Reproduce:
1.
2.
3.
Actual results:
 
Expected results:
 
Mandatory Information for all Bugs:
1 - gluster v <volname> info
2 - gluster v <volname> heal info
3 - gluster v <volname> status
4 - Fuse Mount/SMB/nfs-ganesha/OCS ???
 

Additional info: