Bug 996047

Summary:	volume-replace-brick issues
Product:	[Community] GlusterFS	Reporter:	krishnan parthasarathi <kparthas>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, jbyers, nsathyan, pkoro
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-22 15:46:38 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:
Bug Depends On:	797729, 816915
Bug Blocks:

Description krishnan parthasarathi 2013-08-12 10:04:06 UTC

Description of problem:

Replace-brick data migration algorithm relies on afr (replicate) translator's self-heal mechanism. The algorithm has not been kept up to date with the recent changes in (afr's) self-heal.
Replace-brick command is not failure-friendly. That is to say, the pump translator, which is nothing but the afr translator with a crawler logic, doesn't recover after a crash/shutdown, of the brick process it is part of.

This bug is meant to be the tracker bug, to track issues that are observed in replace-brick command.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Please add bugs that pertain to this tracker bug, to the "Depends on" box.

Comment 1 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC

because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.