Bug 1300977 - No order while taking locks on DHT
Summary: No order while taking locks on DHT
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-22 09:14 UTC by Sakshi
Modified: 2018-10-08 03:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-08 03:23:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Sakshi 2016-01-22 09:14:56 UTC 
Description of problem:
When lock request is sent on DHT, it is taken on any of the cached subvol. Due to this same fop triggered from two different mount points can take lock on different cached subvols and execute parallely. This makes acquiring locks useless.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.