Bug 1262161 - RFE : Feature: Automagic unsplit-brain policies for v3.6.x (cluster/afr)
RFE : Feature: Automagic unsplit-brain policies for v3.6.x (cluster/afr)
Product: GlusterFS
Classification: Community
Component: replicate (Show other bugs)
All All
medium Severity medium
: ---
: ---
Assigned To: rwareing
: FutureFeature, Triaged
Depends On:
Blocks: 1328224 1339639
  Show dependency treegraph
Reported: 2015-09-10 21:57 EDT by rwareing
Modified: 2016-08-23 08:30 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1328224 (view as bug list)
Last Closed: 2016-08-23 08:30:30 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to add automagic split-brain resolution. (33.09 KB, application/mbox)
2015-09-10 21:57 EDT, rwareing
no flags Details

  None (edit)
Description rwareing 2015-09-10 21:57:29 EDT
Created attachment 1072407 [details]
Patch to add automagic split-brain resolution.

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 experience.

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:
Comment 1 rwareing 2015-09-10 22:12:46 EDT
Also, to be clear this patch should patch cleanly to the release-3.6 branch.
Comment 2 Niels de Vos 2016-08-23 08:30:30 EDT
This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.

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