[Bugs] [Bug 1328224] New: RFE : Feature: Automagic unsplit-brain policies for AFR

bugzilla at redhat.com bugzilla at redhat.com
Mon Apr 18 18:52:40 UTC 2016


            Bug ID: 1328224
           Summary: RFE : Feature: Automagic unsplit-brain policies for
           Product: GlusterFS
           Version: mainline
         Component: replicate
          Keywords: FutureFeature, Triaged
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org, rwareing at fb.com, sshreyas at fb.com
        Depends On: 1262161

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

Description of problem:
>From time to time, GlusterFS users, admins (and even developers) can do
unfortunate things to a volume which cause split-brain to files and
directories.  In such cases where the so-called "wise fool" algorithm (aka
change logs) cannot determine a clean version of the file an IO error will be
bubbled up to the user; thus ruining their GlusterFS clustered storage

The present solution for these cases is to go into the backend and delete or
move the copies of the file that aren't desired, or "pinning" to a specific
replica index (which is basically choosing randomly).  For large scale
installations of GlusterFS this really isn't a workable solution, and quite
often a simple heuristic based on time, size or majority will suffice to
resolve things automagically to most end-users satisfaction.

This patch introduces policy based split-brain resolution.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

--- Additional comment from  on 2015-09-10 22:12:46 EDT ---

Also, to be clear this patch should patch cleanly to the release-3.6 branch.

Referenced Bugs:

[Bug 1262161] RFE : Feature: Automagic unsplit-brain policies for v3.6.x
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list