Bug 1212010

Summary:	RFE: `gluster volume heal split-brain' should allow choosing a different source-brick for different kind of heals on the same file
Product:	[Community] GlusterFS	Reporter:	Shruti Sampat <ssampat>
Component:	replicate	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED EOL	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	amukherj, bugs, sasundar
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10:57:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shruti Sampat 2015-04-15 11:58:32 UTC

Description of problem:
------------------------

Currently `gluster volume heal split-brain' command provides a way to choose one source-brick for healing a file. 

It is possible that a file is in data split-brain as well as meta-data split-brain, and the user wants to heal data from a particular brick and meta-data from another. In such a situation, it would help if a different source-brick could be chosen for each type of heal.

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

glusterfs-3.7dev-0.965.git2788ddd.el6.x86_64

How reproducible:
------------------

N/A

Steps to Reproduce:
-------------------

N/A

Actual results:
----------------

The command only allows choosing one source-brick for one file.

Expected results:
-----------------

Allow choosing a different source-brick for different kinds of heals for the same file.

Additional info:

Comment 1 Kaushal 2017-03-08 10:57:06 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.