Bug 1430719 - gfid split brains not getting resolved with automatic splitbrain resolution
Summary: gfid split brains not getting resolved with automatic splitbrain resolution
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Karthik U S
QA Contact:
URL:
Whiteboard:
Depends On: 1416102
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-09 12:19 UTC by Karthik U S
Modified: 2017-05-30 18:47 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.11.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1416102
Environment:
Last Closed: 2017-05-30 18:47:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2017-03-09 13:10:50 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#1) for review on master by Karthik U S (ksubrahm)

Comment 2 Worker Ant 2017-03-21 06:33:10 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#2) for review on master by Karthik U S (ksubrahm)

Comment 3 Worker Ant 2017-03-22 12:01:46 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#3) for review on master by Karthik U S (ksubrahm)

Comment 4 Worker Ant 2017-03-23 05:56:17 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#4) for review on master by Karthik U S (ksubrahm)

Comment 5 Worker Ant 2017-03-24 06:44:10 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#5) for review on master by Karthik U S (ksubrahm)

Comment 6 Worker Ant 2017-03-27 11:10:48 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#6) for review on master by Karthik U S (ksubrahm)

Comment 7 Worker Ant 2017-03-30 07:36:52 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#7) for review on master by Karthik U S (ksubrahm)

Comment 8 Worker Ant 2017-04-17 10:09:36 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#8) for review on master by Karthik U S (ksubrahm)

Comment 9 Worker Ant 2017-04-20 09:41:23 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#9) for review on master by Karthik U S (ksubrahm)

Comment 10 Worker Ant 2017-04-20 14:46:49 UTC
REVIEW: https://review.gluster.org/16878 (cluster/afr: GFID split brain resolution with favorite-child-policy) posted (#10) for review on master by Pranith Kumar Karampuri (pkarampu)

Comment 11 Worker Ant 2017-04-21 00:38:57 UTC
COMMIT: https://review.gluster.org/16878 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 799a2ff8299db6d6dc75f1533f4bd5a3bb72164d
Author: karthik-us <ksubrahm>
Date:   Thu Mar 9 18:08:28 2017 +0530

    cluster/afr: GFID split brain resolution with favorite-child-policy
    
    Problem:
    Currently the automatic split brain resolution with favorite child policy
    is not resolving the GFID split brains.
    
    Fix:
    When there is a GFID split brain and the favorite child policy is set to
    size/mtime/ctime/majority, based on the policy decide on the source and
    sinks. Delete the entry from the sinks and recreate it from the source.
    Mark the appropriate pending attributes and resolve the GFID split brain.
    When the heal takes place it will complete the pending heals and reset
    the attributes.
    
    Change-Id: Ie30e5373f94ca6f276745d9c3ad662b8acca6946
    BUG: 1430719
    Signed-off-by: karthik-us <ksubrahm>
    Reviewed-on: https://review.gluster.org/16878
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Ravishankar N <ravishankar>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 12 Shyamsundar 2017-05-30 18:47:11 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.