[Gluster-devel] mandatory lock

Raghavendra Gowdappa rgowdapp at redhat.com
Thu Jan 8 10:49:26 UTC 2015



----- Original Message -----
> From: "Raghavendra Gowdappa" <rgowdapp at redhat.com>
> To: "Harmeet Kalsi" <kharmeet at hotmail.com>
> Cc: "Gluster-devel at gluster.org" <gluster-devel at gluster.org>
> Sent: Thursday, January 8, 2015 4:12:44 PM
> Subject: Re: [Gluster-devel] mandatory lock
> 
> 
> 
> ----- Original Message -----
> > From: "Harmeet Kalsi" <kharmeet at hotmail.com>
> > To: "Gluster-devel at gluster.org" <gluster-devel at gluster.org>
> > Sent: Wednesday, January 7, 2015 5:55:43 PM
> > Subject: [Gluster-devel] mandatory lock
> > 
> > Dear All.
> > Would it be possible for someone to guide me in the right direction to
> > enable
> > the mandatory lock on a volume please.
> > At the moment two clients can edit the same file at the same time which is
> > causing issues.
> 
> I see code related to mandatory locking in posix-locks xlator (pl_writev,
> pl_truncate etc). To enable it you've to set "option mandatory-locks yes" in
> posix-locks xlator loaded on bricks
> (/var/lib/glusterd/vols/<volname>/*.vol). We've no way to set this option
> through gluster cli. Also, I am not sure to what extent this feature is
> tested/used till now. You can try it out and please let us know whether it
> worked for you :).

If mandatory locking doesn't work for you, can you modify your application to use advisory locking, since advisory locking is tested well and being used for long time?

> 
> > Many thanks in advance
> > Kind Regards
> >  		 	   		  
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> > 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel
> 


More information about the Gluster-devel mailing list