[Bugs] [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

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1385474

SATHEESARAN <sasundar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED



--- Comment #7 from SATHEESARAN <sasundar at redhat.com> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hEm4Jv47G8&a=cc_unsubscribe