On 04/24/2015 06:58 PM, Shyam wrote:
The solution outline is for the rebalance process to migrate the locks,
with some additional coordination with the locks/lease/upcall xlators.
The problem however is _mapping_ all of the lock information across the
2 different storage node brick processes. (i.e client_t information)
Thanks Shyam.
I have opened BZs - 1214644, 1214654 to track these issues. Have posted
both the mail thread links the bug.
-Soumya
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
