Gluster users - Jun 2011 - lock xlator question

Hi everyone,

I just want to understand how the lock xlator handles client failures.
Say one client uses fcntl() to lock a file for write using mandatory
lock, and later it crashes. Is there a lock expiration in lock xlator
to deal with this situation so that others can lock the file later on?
Or everybody is pretty much locked out?

thanks,
- cheng

Lock translator cleans up all locks held by a client when it disconnects. It
is the client's responsibility to re-acquire locks which it had held before
disconnection.

Avati

On Tue, Jun 7, 2011 at 12:36 PM, Cheng Shao <zchshao at gmail.com> wrote:
> Hi everyone,
>
> I just want to understand how the lock xlator handles client failures.
> Say one client uses fcntl() to lock a file for write using mandatory
> lock, and later it crashes. Is there a lock expiration in lock xlator
> to deal with this situation so that others can lock the file later on?
> Or everybody is pretty much locked out?
>
> thanks,
> - cheng
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110610/aa079168/attachment.html>