Bug 1020230 - [AFR][RFE]: Need a definitive way to figure out if SELF HEAL has completed on a volume
Summary: [AFR][RFE]: Need a definitive way to figure out if SELF HEAL has completed on...
Keywords:
Status: CLOSED DUPLICATE of bug 986317
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: replicate
Version: 2.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 10:28 UTC by Sachidananda Urs
Modified: 2016-09-17 12:12 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.6.0-3.0.el6rhs
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-14 06:16:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Sachidananda Urs 2013-10-17 10:28:02 UTC
Description of problem:

While doing rolling upgrades, as a first step we bring down one of the nodes and upgrade it. And to continue upgrading the replica, we wait till the data is self-healed on the node which was brought down. However, currently the heal info command does not definitively provide information whehter self-heal is complete.

Ref: Bug: 986317

Comment 1 Sachidananda Urs 2013-10-17 10:28:26 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=986317

Comment 2 Sachidananda Urs 2013-10-17 10:34:22 UTC
[root@boggs ~]# gluster volume heal pure_gold info|wc -l
152
[root@boggs ~]# gluster volume heal pure_gold info|wc -l
16
[root@boggs ~]# gluster volume heal pure_gold info|wc -l
51
[root@boggs ~]# gluster volume heal pure_gold info|wc -l
153
[root@boggs ~]# gluster volume heal pure_gold info|wc -l
190
[root@boggs ~]# gluster volume heal pure_gold info|wc -l
145

The output is very inconsistent.

Comment 4 Sachidananda Urs 2013-10-17 11:14:15 UTC
Upon self-heal completion, a status message like. All entries self-healed, nothing more to self-heal... should be useful.

Comment 5 Pranith Kumar K 2014-05-14 06:16:09 UTC

*** This bug has been marked as a duplicate of bug 986317 ***


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