Bug 762286 (GLUSTER-554)

Summary:	Replicate only writes posix locks to first subvolume
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joej>
Component:	replicate	Assignee:	Vikas Gorur <vikas>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0.0	CC:	aavati, anush, gluster-bugs, jdarcy
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joe Julian 2010-01-21 20:02:54 UTC

Replicate only writes locks to the first subvolume. This behavior causes a single point of failure. At minimum there should be an option to replicate the posix locks to all subvolumes.

Comment 1 Vikas Gorur 2010-01-22 03:16:49 UTC

Replicate indeed sends the posix locks request to all its subvolumes.

Can you clarify why you arrived at the opposite conclusion?

Comment 2 Jeff Darcy 2010-01-22 11:45:33 UTC

That one was probably my fault.  I observed that afr_lk only seemed to be sending the request to one subvolume.  However, I now see that the callback sends it to the next, etc.  Is there any reason this needs to be done sequentially rather than in parallel?

Comment 3 Anand Avati 2010-01-23 08:36:15 UTC

> That one was probably my fault.  I observed that afr_lk only seemed to be
> sending the request to one subvolume.  However, I now see that the callback
> sends it to the next, etc.  Is there any reason this needs to be done
> sequentially rather than in parallel?

Acquiring locks in parallel can lead to a race among multiple clients both getting granted conflicting locks. Sequential acquisition is safe.

Avati