[Bugs] [Bug 1266876] cluster/afr: AFR2 returns empty readdir results to clients if brick is added back into cluster after re-imaging /formatting

[bugzilla at redhat.com]

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



--- Comment #15 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/12250 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit 936f8aeac3252951e7fa0cdaa5d260fad3bd5ea0
Author: Anuradha Talur <atalur at redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd : Introduce reset brick

    The command basically allows replace brick with src and
    dst bricks as same.

    Usage:
    gluster v reset-brick <volname> <hostname:brick-path> start
    This command kills the brick to be reset. Once this command is run,
    admin can do other manual operations that they need to do,
    like configuring some options for the brick. Once this is done,
    resetting the brick can be continued with the following options.

    gluster v reset-brick <vname> <hostname:brick> <hostname:brick> commit
{force}

    Does the job of resetting the brick. 'force' option should be used
    when the brick already contains volinfo id.

    Problem: On doing a disk-replacement of a brick in a replicate volume
    the following 2 scenarios may occur :

    a) there is a chance that reads are served from this replaced-disk brick,
    which leads to empty reads. b) potential data loss if next writes succeed
    only on replaced brick, and heal is done to other bricks from this one.

    Solution: After disk-replacement, make sure that reset-brick command is
    run for that brick so that pending markers are set for the brick and it
    is not chosen as source for reads and heal. But, as of now replace-brick
    for the same brick-path is not allowed. In order to fix the above
    mentioned problem, same brick-path replace-brick is needed.
    With this patch reset-brick commit {force} will be allowed even when
    source and destination <hostname:brickpath> are identical as long as
    1) destination brick is not alive
    2) source and destination brick have the same brick uuid and path.
    Also, the destination brick after replace-brick will use the same port
    as the source brick.

    Change-Id: I440b9e892ffb781ea4b8563688c3f85c7a7c89de
    BUG: 1266876
    Signed-off-by: Anuradha Talur <atalur at redhat.com>
    Reviewed-on: http://review.gluster.org/12250
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey at redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>

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