diff options
| author | Ashish Pandey <aspandey@redhat.com> | 2018-07-27 14:53:30 +0530 |
|---|---|---|
| committer | Ravishankar N <ravishankar@redhat.com> | 2018-08-31 06:50:22 +0000 |
| commit | 19436f2e5fa6dc7f33b7d32d170d3c18f5fdd0d4 (patch) | |
| tree | 4ebcfe3cc863a844ace64de89bdaae510a7d4d05 /extras/thin-arbiter | |
| parent | cd1051789361bd07e248baf1bf0fbbe479cd4ae1 (diff) | |
thin arbiter: set notify-contention option to yes
If this option is "ON' and if there is a lock contention for
a file from 2 clients/self-heal daemon, an up call will
be sent to all the clients holding that locks. Clients
can handle this notification and may release the locks
at the right time asap.
If this option is ON, we get "instant" lock contention
notification on client side.
In next version of thin arbiter, we need to implement
lock contention notification handling and two domain
locking to synchronize update/access of xattrs of thin arbiter
replica id file. This option is an efficient way to find
out lock contention. In this case it is also helping to
implement two domain locking for replica id file.
Change-Id: I69883898d52feb425dfceb31cf12fa2157aaa314
fixes bz#1609207
Signed-off-by: Ashish Pandey <aspandey@redhat.com>
Diffstat (limited to 'extras/thin-arbiter')
| -rw-r--r-- | extras/thin-arbiter/thin-arbiter.vol | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/extras/thin-arbiter/thin-arbiter.vol b/extras/thin-arbiter/thin-arbiter.vol index 7a60f179891..244a4caf485 100644 --- a/extras/thin-arbiter/thin-arbiter.vol +++ b/extras/thin-arbiter/thin-arbiter.vol @@ -10,6 +10,7 @@ end-volume volume ta-locks type features/locks + option notify-contention yes subvolumes ta-thin-arbiter end-volume |