----- Original Message ----- > From: "Raghavendra Gowdappa" <rgowd...@redhat.com> > To: "Harmeet Kalsi" <kharm...@hotmail.com> > Cc: "Gluster-devel@gluster.org" <gluster-devel@gluster.org> > Sent: Thursday, January 8, 2015 4:12:44 PM > Subject: Re: [Gluster-devel] mandatory lock > > > > ----- Original Message ----- > > From: "Harmeet Kalsi" <kharm...@hotmail.com> > > To: "Gluster-devel@gluster.org" <gluster-devel@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@gluster.org > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
