Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1256909

Summary:	Unable to examine file in metadata split-brain after setting `replica.split-brain-choice' attribute to a particular replica
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	replicate	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.3	CC:	atalur, bugs, gluster-bugs, nsathyan, ssampat, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1240244	Environment:
Last Closed:	2015-09-09 09:40:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1238398, 1240244
Bug Blocks:

Comment 1 Anand Avati 2015-08-25 17:36:19 UTC

REVIEW: http://review.gluster.org/12011 (cluster/afr : Examine data/metadata readable for read-subvol During lookup and discover, currently read_subvol is based only on data_readable. read_subvol should be decided based on both data_readable and metadata_readable.) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2015-08-28 07:13:19 UTC

COMMIT: http://review.gluster.org/12011 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 12649804d0c830bc17b685b904825e03b0e968cd
Author: Anuradha Talur <atalur>
Date:   Mon Aug 3 17:09:13 2015 +0530

    cluster/afr : Examine data/metadata readable for read-subvol
    During lookup and discover, currently read_subvol is based
    only on data_readable. read_subvol should be decided based
    on both data_readable and metadata_readable.
    
    Credits to Ravishankar N for the logic of afr_first_up_child
    from http://review.gluster.org/10905/ .
    
    > Change-Id: I98580b23c278172ee2902be08eeaafb6722e830c
    > BUG: 1240244
    > Signed-off-by: Anuradha Talur <atalur>
    > Reviewed-on: http://review.gluster.org/11551
    > Reviewed-by: Ravishankar N <ravishankar>
    > Tested-by: Gluster Build System <jenkins.com>
    > Reviewed-by: Krutika Dhananjay <kdhananj>
    > Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    > (cherry picked from commit 36349fa250ace6109002dfa41305d9dcd54ce0a9)
    
    Change-Id: Ia068ef9deb97f7bc48ea0c56d5ab6851f8860118
    BUG: 1256909
    Signed-off-by: Anuradha Talur <atalur>
    Reviewed-on: http://review.gluster.org/12011
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>

Comment 3 Kaushal 2015-09-09 09:40:44 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.7.4, please open a new bug report.

glusterfs-3.7.4 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12496
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user