[Bugs] [Bug 1633625] New: split-brain observed on parent dir

[bugzilla at redhat.com]

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

            Bug ID: 1633625
           Summary: split-brain observed on parent dir
           Product: GlusterFS
           Version: 3.12
         Component: replicate
          Keywords: Translation
          Severity: low
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org, pasik at iki.fi
        Depends On: 1626994



+++ This bug was initially created as a clone of Bug #1626994 +++

Description of problem:

Reported downstream via BZ 1610743.
When a directory only has dirty xattrs set (due to fop failing due to quorum
not met, say), heal-info shows the directory to be in split-brain. After heal
is over, it goes away though,

--- Additional comment from Worker Ant on 2018-09-10 05:15:02 EDT ---

REVIEW: https://review.gluster.org/21135 (afr: don't consider 'dirty' as
split-brain in heal info) posted (#1) for review on master by Ravishankar N

--- Additional comment from Worker Ant on 2018-09-21 12:36:02 EDT ---

COMMIT: https://review.gluster.org/21135 committed in master by "Shyamsundar
Ranganathan" <srangana at redhat.com> with a commit message- afr: fix incorrect
reporting of directory split-brain

Problem:
When a directory has dirty xattrs due to failed post-ops or when
replace/reset brick is performed, AFR does a conservative merge as
expected, but heal-info reports it as split-brain because there are no
clear sources.

Fix:
Modify pending flag to contain information about pending heals and
split-brains. For directories, if spit-brain flag is not set,just show
them as needing heal and not being in split-brain.

Fixes: bz#1626994
Change-Id: I09ef821f6887c87d315ae99e6b1de05103cd9383
Signed-off-by: Ravishankar N <ravishankar at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1626994
[Bug 1626994] split-brain observed on parent dir
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.