[Bugs] [Bug 1717754] New: Enabled features.locks-notify-contention by default
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jun 6 06:28:32 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1717754
Bug ID: 1717754
Summary: Enabled features.locks-notify-contention by default
Product: GlusterFS
Version: mainline
Status: NEW
Component: locks
Assignee: bugs at gluster.org
Reporter: jahernan at redhat.com
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Description of problem:
Currently 'features.locks-notify-contention' is disabled by default. This
option, when enabled, instructs the locks xlator to send an upcall notification
to the current owner of a lock whenever another client tries to acquire a
conflicting lock.
Both AFR and EC support this notification and react by releasing the lock as
soon as possible. This is extremely useful when eager-lock is enabled (it is by
default) because it allows AFR and EC to use it to improve performance but we
don't loose performance on other clients when access to the same resource is
required.
Since eager-lock is enabled by default, it doesn't make sense to keep
contention notification disabled.
Version-Release number of selected component (if applicable): mainline
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list