Bug 1177737

Summary:	[AFR-V2] - Self-healing from mounts happens even when {metadata,entry,data}-self-heal is disabled.
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	replicate	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs
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-05-30 05:22:52 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 Krutika Dhananjay 2014-12-30 07:27:43 UTC

Description of problem:

In AFR-V1, there is a way to disable client-side healing by setting metadata-self-heal, entry-self-heal and/or data-self-heal to off. However, in afr-v2, even after disabling these options, the normal mounts perform self-heal as part of lookup, which is not desired, for example in cases where the file being looked up is a vm image and needs self-healing of the order of several GBs to be performed from the client, or a directory being healed has several entries to be recreated on the other replicas as part of lookups, which could cause the mount to perceive slowness.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Krutika Dhananjay 2015-05-30 05:22:52 UTC

Another BZ @ https://bugzilla.redhat.com/show_bug.cgi?id=1226507 was raised today independently for the same issue. Will close this as a duplicate.

*** This bug has been marked as a duplicate of bug 1226507 ***