[Bugs] [Bug 1320412] disperse: Provide an option to enable/disable eager lock

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1320412


--- Doc Text *updated* by Ashish Pandey <aspandey at redhat.com> ---
Cause: 

If a fop takes lock, and completes its operation, it waits for 1 second before releasing the lock. However, If ec find any lock contention within this time period, it release the lock immediately before time expires. As we take lock on first brick, for few operations, like read, it might happen that discovery of lock contention might take long time and can degrades the performance. 

Consequence: 
Poor performance in data/metadata read.

Fix: 

Provide an option to enable/disable eager lock. If eager lock is disabled, lock will be released as soon as fop completes. 

Result: 

gluster v set <VOLUME NAME> disperse.eager-lock on 
gluster v set <VOLUME NAME> disperse.eager-lock off


-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=xgPYfGIw3i&a=cc_unsubscribe