[Bugs] [Bug 1435656] Disperse: Provide description of disperse.eager-lock option.

[bugzilla at redhat.com]

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

nchilaka <nchilaka at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED



--- Comment #6 from nchilaka <nchilaka at redhat.com> ---
Before Fix:
(glusterfs-server-3.8.4-22.el7rhgs.x86_64)

Option: disperse.eager-lock
Default Value: on
Description: This option will enable/diable eager lock fordisperse volume 


Post fix(3.8.4-24)
Option: disperse.eager-lock
Default Value: on
Description: Enable/Disable eager lock for disperse volume. If a fop takes a
lock and completes its operation, it waits for next 1 second before releasing
the lock, to see if the lock can be reused for next fop from the same client.
If ec finds any lock contention within 1 second it releases the lock
immediately before time expires. This improves the performance of file
operations.However, as it takes lock on first brick, for few operations like
read, discovery of lock contention might take long time and can actually
degrade the performance. If eager lock is disabled, lock will be released as
soon as fop completes. 



Looking good , hence moving to verified.
However I see that we can set any junk(non boolean) value to this option, I
will raise a seperate bug (not a regression)

-- 
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=gzpNBRV3Nb&a=cc_unsubscribe