Bug 1385474 - [granular entry sh] - Provide a CLI to enable/disable the feature that checks that there are no heals pending before allowing the operation
Summary: [granular entry sh] - Provide a CLI to enable/disable the feature that checks...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: replicate
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.2.0
Assignee: Krutika Dhananjay
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1370410 1398500 1398501
Blocks: 1351528
TreeView+ depends on / blocked
 
Reported: 2016-10-17 07:06 UTC by Krutika Dhananjay
Modified: 2017-03-23 06:10 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.8.4-6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1370410
Environment:
Last Closed: 2017-03-23 06:10:41 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0486 0 normal SHIPPED_LIVE Moderate: Red Hat Gluster Storage 3.2.0 security, bug fix, and enhancement update 2017-03-23 09:18:45 UTC

Description Krutika Dhananjay 2016-10-17 07:06:59 UTC 
+++ This bug was initially created as a clone of Bug #1370410 +++

Description of problem:

Same as Summary.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Krutika Dhananjay 2016-10-28 07:23:53 UTC 
Have posted the patch on master for review - http://review.gluster.org/#/c/15747/1
It still needs lot of testing and reviews. Moving this bug to POST state in any case.
Comment 5 Krutika Dhananjay 2016-11-28 10:08:30 UTC 
https://code.engineering.redhat.com/gerrit/91373 and https://code.engineering.redhat.com/gerrit/91374
Comment 7 SATHEESARAN 2016-12-15 07:28:31 UTC 
Tested with RHGS 3.2.0 interim build ( glusterfs-3.8.4-8.el7rhgs ).

When the volume state is 'created'. volume set command could be used to enable granular-entry-heal on the volume.
Once the volume is started, then enabling granular-entry-heal via volume set throws helpful message to use 'gluster volume heal' for enabling granular entry heal.

[root@~]# gluster volume set engine cluster.granular-entry-heal on
volume set: failed:  'gluster volume set <VOLNAME> cluster.granular-entry-heal {enable, disable}' is not supported. Use 'gluster volume heal <VOLNAME> granular-entry-heal {enable, disable}' instead.

I could able to enable granular-entry-heal using 'gluster volume heal'
as follows:
[root@ ~]# gluster volume heal engine granular-entry-heal enable
Enable granular entry heal on volume engine has been successful 

[root@ ~]# gluster volume get engine cluster.granular-entry-heal
Option                                  Value                                   
------                                  -----                                   
cluster.granular-entry-heal             on    

When the granular-entry-heal is enabled on the volume, while self-heal is in progress, proper warning is being thrown:

[root@]# gluster volume heal rep3vol granular-entry-heal enable
One or more entries need heal. Please execute the command again after there are no entries to be healed
Volume heal failed.
Comment 9 errata-xmlrpc 2017-03-23 06:10:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0486.html
Note You need to log in before you can comment on or make changes to this bug.