Bug 1084585 - There needs to be a cli method of determining if heal full has completed
Summary: There needs to be a cli method of determining if heal full has completed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-04 18:57 UTC by Joe Julian
Modified: 2017-03-07 18:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-07 18:26:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Joe Julian 2014-04-04 18:57:23 UTC
When running "gluster volume heal $vol full" there's no way to know if it has completed.

There needs to be some way of checking the status of that command.

Comment 1 Ravishankar N 2017-03-07 08:31:46 UTC
Hi Joe, 'gluster volume heal $vol statistics` set of commands should help here. It also prints full heal statistics in addition to the index heal ones:


------------------------------------------------------------
$gluster  v heal volname statistics
<snip>
Starting time of crawl: Tue Mar  7 13:56:05 2017

Crawl is in progress
Type of crawl: FULL
No. of entries healed: 303
No. of entries in split-brain: 0
No. of heal failed entries: 608
<\snip>
------------------------------------------------------------
$gluster v heal volname statistics
<snip>
Starting time of crawl: Tue Mar  7 13:56:05 2017

Ending time of crawl: Tue Mar  7 13:57:56 2017

Type of crawl: FULL
No. of entries healed: 783
No. of entries in split-brain: 0
No. of heal failed entries: 1777
<\snip>

------------------------------------------------------------

Is this what you are looking for?

Comment 2 Joe Julian 2017-03-07 18:26:43 UTC
Yes, that's new since 2014. :)


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