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.<div><br></div><div>Avati<br><br><div class="gmail_quote">
On Tue, Jun 7, 2011 at 12:36 PM, Cheng Shao <span dir="ltr"><<a href="mailto:zchshao@gmail.com">zchshao@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi everyone,<br>
<br>
I just want to understand how the lock xlator handles client failures.<br>
Say one client uses fcntl() to lock a file for write using mandatory<br>
lock, and later it crashes. Is there a lock expiration in lock xlator<br>
to deal with this situation so that others can lock the file later on?<br>
Or everybody is pretty much locked out?<br>
<br>
thanks,<br>
- cheng<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://gluster.org/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://gluster.org/cgi-bin/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br></div>