Bug 1025411 - Enhancement: Self Heal Selection Automation
Summary: Enhancement: Self Heal Selection Automation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 15:42 UTC by Dean Bruhn
Modified: 2015-12-08 12:45 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-08 12:45:19 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Dean Bruhn 2013-10-31 15:42:55 UTC
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):
3.3.2

How reproducible:


Steps to Reproduce:
1.
2.
3.

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 12:45:19 UTC
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.