Bug 1290306 - [RFE]eager-locking as a feature needs to be implemented
Summary: [RFE]eager-locking as a feature needs to be implemented
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-10 07:05 UTC by Pranith Kumar K
Modified: 2017-03-06 06:51 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-06 06:51:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Pranith Kumar K 2015-12-10 07:05:18 UTC 
Description of problem:
we need a feature which reduces the number of network round trips. One way is to take full locks on file/directory and delay their unlock so that next modification operations can reuse them without going over network.

Note: The design may change as it is under discussion on #gluster-dev with xavi and Krutika.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Pranith Kumar K 2017-03-06 06:51:39 UTC 
EC also already has eager-lock, so it doesn't make much sense to implement this feature now.
Note You need to log in before you can comment on or make changes to this bug.