[Bugs] [Bug 1327863] cluster/afr: Fix partial heals in 3-way replication

bugzilla at redhat.com bugzilla at redhat.com
Sun Apr 17 02:02:41 UTC 2016


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



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14008 committed in release-3.7 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit 6b88d97c4a9e999180d77463e38ad14fc9d944cf
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Thu Mar 17 19:42:00 2016 +0530

    cluster/afr: Fix partial heals in 3-way replication

    Problem:
    When there are 2 sources and one sink and if two self-heal daemons
    try to acquire locks at the same time, there is a chance that it
    gets a lock on one source and sink leading partial to heal. This will
    need one more heal from the remaining source to sink for the complete
    self-heal. This is not optimal.

    Fix:
    Upgrade non-blocking locks to blocking lock on all the subvolumes, if
    the number of locks acquired is majority and there were eagains.

     >BUG: 1318751
     >Change-Id: Iae10b8d3402756c4164b98cc49876056ff7a61e5
     >Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
     >Reviewed-on: http://review.gluster.org/13766
     >Smoke: Gluster Build System <jenkins at build.gluster.com>
     >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
     >CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
     >Reviewed-by: Ravishankar N <ravishankar at redhat.com>
     >(cherry picked from commit 8deedef565df49def75083678f8d1558c7b1f7d3)

    Change-Id: Ia164360dc1474a717f63633f5deb2c39cc15017c
    BUG: 1327863
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/14008
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.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=pRHcTCUF2O&a=cc_unsubscribe


More information about the Bugs mailing list