[Bugs] [Bug 1367272] [HC]: After bringing down and up of the bricks VM' s are getting paused

[bugzilla at redhat.com]

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



--- Comment #7 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15221 committed in release-3.8 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit d99f72842595306e9f26a275804bf0f310caba53
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date:   Thu Jul 28 21:29:59 2016 +0530

    cluster/afr: Prevent split-brain when bricks are brought off and on in
cyclic order

            Backport of: http://review.gluster.org/15080

    When the bricks are brought offline and then online in cyclic
    order while writes are in progress on a file, thanks to inode
    refresh in write txns, AFR will mostly fail the write attempt
    when the only good copy is offline. However, there is still a
    remote possibility that the file will run into split-brain if
    the brick that has the lone good copy goes offline *after* the
    inode refresh but *before* the write txn completes (I call it
    in-flight split-brain in the patch for ease of reference),
    requiring intervention from admin to resolve the split-brain
    before the IO can resume normally on the file. To get around this,
    the patch does the following things:
    i) retains the dirty xattrs on the file
    ii) avoids marking the last of the good copies as bad (or accused)
        in case it is the one to go down during the course of a write.
    iii) fails that particular write with the appropriate errno.

    This way, we still have one good copy left despite the split-brain
situation
    which when it is back online, will be chosen as source to do the heal.

    > Change-Id: I9ca634b026ac830b172bac076437cc3bf1ae7d8a
    > BUG: 1363721
    > Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    > Reviewed-on: http://review.gluster.org/15080
    > Tested-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    > Smoke: Gluster Build System <jenkins at build.gluster.org>
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    > Reviewed-by: Ravishankar N <ravishankar at redhat.com>
    > Reviewed-by: Oleksandr Natalenko <oleksandr at natalenko.name>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    (cherry picked from commit fcb5b70b1099d0379b40c81f35750df8bb9545a5)

    Change-Id: I157f1025aebd6624fa3d412abc69a4ae6f2fe9e0
    BUG: 1367272
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    Signed-off-by: Oleksandr Natalenko <oleksandr at natalenko.name>
    Reviewed-on: http://review.gluster.org/15221
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Smoke: 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.