Bug 1212010 - RFE: `gluster volume heal split-brain' should allow choosing a different source-brick for different kind of heals on the same file
Summary: RFE: `gluster volume heal split-brain' should allow choosing a different sour...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-15 11:58 UTC by Shruti Sampat
Modified: 2017-03-08 10:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:57:06 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


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