Bug 1416102

Summary: gfid split brains not getting resolved with automatic splitbrain resolution
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nag Pavan Chilakam <nchilaka>
Component: replicateAssignee: Karthik U S <ksubrahm>
Status: CLOSED WONTFIX QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: urgent Docs Contact:
Priority: high    
Version: rhgs-3.2CC: amukherj, ksubrahm, ravishankar, rcyriac, rhs-bugs, storage-qa-internal
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1430719 (view as bug list) Environment:
Last Closed: 2018-11-16 05:49:31 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:    
Bug Blocks: 1304593, 1430719, 1472361    

Description Nag Pavan Chilakam 2017-01-24 15:26:29 UTC
Description of problem:
=======================
as part of RFE testing of bz# 1304593 - Split-brain occurring with one cable pull
I tried to check if the gfid split brain gets resolved based on different policies.

However It doesn't get resolved when i set the cluster.favorite-child-policy to mtime







Version-Release number of selected component (if applicable):
=========
3.8.4-11


How reproducible:
=======
always

Steps to Reproduce:
1.set cluster.favorite-child-policy to say mtime
2.create a gfid split brain situation
3.now check if the automatic healing feature resolves this 

the split brain is not resolved and hence IO error on client as below
[root@dhcp35-196 rep]# ll
ls: cannot access f1: Input/output error
total 1
-?????????? ? ?    ?     ?            ? f1

Comment 3 Atin Mukherjee 2017-03-09 14:18:53 UTC
upstream patch : https://review.gluster.org/16878

Comment 6 Atin Mukherjee 2018-11-12 02:23:15 UTC
Isn't the patch already part of 3.4.0? Does it need only qualification? Can we please take this bug to the closure?

Comment 7 Karthik U S 2018-11-13 05:26:15 UTC
Hi Atin,

Even though the patch is part of 3.4.0, the automatic split-brain resolution policy as a feature (BZ #1304593) has failed-qa. It needs some improvements and bug fixes. Currently the feature itself is not qualified. Since this bug is going to be fixed using the same policies, I think it is better to wait for the other issues to be fixed in the feature before qualifying this.

Thanks,
Karthik