Bug 1114415 - There is no way to monitor if the healing is successful when the brick is erased
Summary: There is no way to monitor if the healing is successful when the brick is erased
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1117169
TreeView+ depends on / blocked
 
Reported: 2014-06-30 03:27 UTC by Pranith Kumar K
Modified: 2017-08-23 06:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1117169 (view as bug list)
Environment:
Last Closed: 2017-08-23 06:33:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Pranith Kumar K 2014-06-30 03:27:24 UTC 
Description of problem:

When "gluster volume heal <volname> full" is issued, there is no way to figure out if the healing is complete on the brick that is erased. This makes it very hard for users to confirm the self-heal is complete.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Pranith Kumar K 2015-08-27 13:30:16 UTC 
With the new replace-brick implementation this bug is not applicable any more as '/' will be needing heal as soon as replace-brick is successful.
Comment 2 Karthik U S 2017-08-23 06:33:11 UTC 
Closing the bug as per comment #1.
Note You need to log in before you can comment on or make changes to this bug.