Bug 847677

Summary:	[FEAT] granular entry self-heal
Product:	[Community] GlusterFS	Reporter:	Venky Shankar <vshankar>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs, jdarcy, rwheeler
Target Milestone:	---	Keywords:	FutureFeature, Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	850509 (view as bug list)		Environment:
Last Closed:	2016-08-16 13:08:47 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:
Bug Blocks:	850509, 852944, 1117822

Description Venky Shankar 2012-08-13 09:23:25 UTC

making the entry self-heal granular (i.e. locks taken on basename + file instead of basename) would result in less contention on it and speed up parallel operation that are in progress.

Comment 1 Jeff Darcy 2013-01-22 12:31:13 UTC

Removing from 3.4 alpha list (per meeting).

Comment 2 Pranith Kumar K 2014-05-25 10:16:12 UTC

This is already present in afrv2 upstream.

Comment 3 Niels de Vos 2016-08-16 13:08:47 UTC

(In reply to Pranith Kumar K from comment #2)
> This is already present in afrv2 upstream.

This is included in glusterfs-3.7 and beyond.

This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.