Bug 1609207

Summary:	thin arbiter: set notify-contention option to yes
Product:	[Community] GlusterFS	Reporter:	Ashish Pandey <aspandey>
Component:	replicate	Assignee:	Ashish Pandey <aspandey>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, pasik
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:15:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ashish Pandey 2018-07-27 09:26:14 UTC

Description of problem:

thin arbiter: set notify-contention option to yes


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
thin arbiter: set notify-contention option to yes

Additional info:

Comment 1 Worker Ant 2018-07-27 09:28:51 UTC

REVIEW: https://review.gluster.org/20577 (thin arbiter: set notify-contention option to yes) posted (#1) for review on master by Ashish Pandey

Comment 2 Worker Ant 2018-08-31 06:50:59 UTC

COMMIT: https://review.gluster.org/20577 committed in master by "Ravishankar N" <ravishankar> with a commit message- 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>

Comment 3 Shyamsundar 2018-10-23 15:15:49 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/