Bug 1332568 - [granular entry sh] - Use compound fop to reduce number of fops over the network
Summary: [granular entry sh] - Use compound fop to reduce number of fops over the network
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Krutika Dhananjay
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 13:28 UTC by Krutika Dhananjay
Modified: 2018-10-31 04:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-31 04:46:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.