[Bugs] [Bug 1459530] [RFE] Need a way to resolve gfid split brains

[bugzilla at redhat.com]

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



--- Comment #14 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17485 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit 657d78dbad118e511e1fca8b1badb9f8ae7a6f60
Author: karthik-us <ksubrahm at redhat.com>
Date:   Wed Jun 7 15:56:13 2017 +0530

    cluster/afr: GFID split-brain resolution with existing CLI

    Problem:
    Currently there is no way for the admin from CLI to resolve gfid
    split-brain based on some policy like choice of the brick, mtime
    or size.

    Fix:
    With the existing CLI options based on size, mtime, and choice of
    brick, we do lookup on the parent for the specified file. As
    part of the lookup, if we find gfid mismatch, we resolve them
    based on the policy and return. If the file is not in gfid split-
    brain, then we check for the data and metadata split-brain in the
    getxattr code path, and resolve if any.

    This will work provided absolute path to the file with the CLI
    and not with gfid of the file. Hence the source-brick policy
    without any file path will also not resolve the gfid split-brain
    since it uses the gfid of the files. But it can resolve any other
    type of split-brains and skip the gfid mismatch resolution with
    the usual error message.

    Reverting the change https://review.gluster.org/17290. This patch
    resolves the issue.

    Fixes gluster/glusterfs#135

    Change-Id: Iaeba6fc32f184a34255d03be87cda02773130a09
    BUG: 1459530
    Signed-off-by: karthik-us <ksubrahm at redhat.com>
    Reviewed-on: https://review.gluster.org/17485
    Reviewed-by: Ravishankar N <ravishankar at redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>

-- 
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=UFQQGYr5Bs&a=cc_unsubscribe