Bug 1332568

Summary:	[granular entry sh] - Use compound fop to reduce number of fops over the network
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	replicate	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, pkarampu
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-31 04:46:23 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 2016-05-03 13:28:43 UTC

Description of problem:

Every entry self-heal is preceded by a full lock on the parent dir until this entry is created/deleted on the sink(s). With granular entry sh, this would be additionally followed by the purging of the index associated with the entry name using an unlink over the network. The UNLOCK after the heal and the unlink to purge the index can be clubbed together into one single compound fop for even better performance.

This bug is to track that change.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Krutika Dhananjay 2018-10-31 04:46:23 UTC

Closing this bug as compound fops itself is on its way to being deprecated.