Bug 1025411 - Enhancement: Self Heal Selection Automation
Enhancement: Self Heal Selection Automation
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
All Unspecified
medium Severity low
: ---
: ---
Assigned To: Pranith Kumar K
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-10-31 11:42 EDT by Dean Bruhn
Modified: 2015-12-08 07:45 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-08 07:45:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dean Bruhn 2013-10-31 11:42:55 EDT
Description of problem:
Currently when Gluster needs you to manually select which file is the correct file and do some maintenance on the brick side to correct the issue. 

In instances where thousands of files are in a split-brain state this can become burdensome. 

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

How reproducible:

Steps to Reproduce:

Actual results:
I/O error

Expected results:
The system to be able to automate the resolution of the split brain scenario based on administrator configurable information such as file size, last modified time, etc. It would be advisable to move the conflicts to a temporary storage place for later review if need be, and create an alert list for the administrator to review, so they can if need be determine the correct file at a later time, or correct an issue that the automation corrected correctly based on the settings but incorrectly based on the needs. 

Additional info:
Comment 1 Ravishankar N 2015-12-08 07:45:19 EST
Recent versions of gluster have support for resolving splitbrains via gluster CLI and  from the (fuse) mount point as well. See https://github.com/gluster/glusterfs-specs/blob/master/done/Features/heal-info-and-split-brain-resolution.md for more information.

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