[Gluster-devel] Posix lock migration design

Susant Palai spalai at redhat.com
Mon Feb 29 07:22:49 UTC 2016

Hi Raghavendra,
   I have a question on the design.

   Currently in case of a client disconnection, pl_flush cleans up the locks associated with the fd created from that client.
>From the design, rebalance will migrate the locks to the new destination. Now in case client gets disconnected from the
destination brick, how it is supposed to clean up the locks as rebalance/brick have no idea whether the client has opened
an fd on destination and what the fd is.

   So the question is how to associate the client fd with locks on destination.


----- Original Message -----
From: "Susant Palai" <spalai at redhat.com>
To: "Gluster Devel" <gluster-devel at gluster.org>
Sent: Friday, 29 January, 2016 3:15:14 PM
Subject: [Gluster-devel] Posix lock migration design

   Here, [1]
is a google document about proposal for "POSIX_LOCK_MIGRATION". Problem statement and design are explained in the document it self.

  Requesting the devel list to go through the document and comment/analyze/suggest, to take the thoughts forward (either on the
google doc itself or here on the devel list).

Gluster-devel mailing list
Gluster-devel at gluster.org

More information about the Gluster-devel mailing list