[Bugs] [Bug 1398501] [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=1398501



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15942 committed in release-3.8 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit e06f4590616dfe7b93e8ac147ed812756df4f22d
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date:   Thu Sep 22 16:48:54 2016 +0530

    cluster/afr: CLI for granular entry heal enablement/disablement

            Backport of: http://review.gluster.org/15747
    When there are already existing non-granular indices created that are
    yet to be healed, if granular-entry-heal option is toggled from 'off' to
    'on', AFR self-heal whenever it kicks in, will try to look for granular
    indices in 'entry-changes'. Because of the absence of name indices,
    granular entry healing logic will fail to heal these directories, and
    worse yet unset pending extended attributes with the assumption that
    are no entries that need heal.

    To get around this, a new CLI is introduced which will invoke glfsheal
    program to figure whether at the time an attempt is made to enable
    granular entry heal, there are pending heals on the volume OR there
    are one or more bricks that are down. If either of them is true, the
    command will be failed with the appropriate error.

    New CLI: gluster volume heal <VOL> granular-entry-heal {enable,disable}

    Change-Id: I342e0390f847fcb015a50ef58aedfcbcb58f4ed3
    BUG: 1398501
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    Reviewed-on: http://review.gluster.org/15942
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.