As per the latest design/implementation changes, since the
cache-invalidation and lease-lock states are maintained separately (in
different inode contexts) and there is no correlation between these two
use-cases, we have decided to move lease-lk changes into a separate
xlator to avoid conflicts between the two and for better maintenance of
the code.
Thanks,
Soumya
On 04/16/2015 05:07 PM, Soumya Koduri wrote:
Hi,
Below link contains the lease-lock design notes (as per the latest
discussion we had). Thanks to everyone involved (CC'ed).
http://www.gluster.org/community/documentation/index.php/Features/Upcall-infrastructure#delegations.2Flease-locks
Kindly go through the same and provide us your inputs.
Thanks,
Soumya
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
