On 18/10/14 20:31, Justin Clift wrote:
----- Original Message -----
<snip>
Right now, distributed-geo-rep has bunch of known issues with deletes
and renames. Part of the issue was solved with a patch sent to upstream
recently. But still it doesn't solve complete issue.
<snip>
Do we have an idea when the "complete solution" to this might be ready
for testing?
The solution involves "changelog crash consistency" among other things.
Since this feature itself is targeted for glusterfs-3.7, I would say the
complete solution would be available with glusterfs-3.7
One the major challenges in solving it involves ordering/sequencing the
fops that happen on the master volume. Because of the distributed nature
of glusterfs and geo-rep, coordinating between gsyncds for proper
ordering of fops is hard.
I have cc'd Aravinda who is the maintainer of geo-rep. He would have
more details.
Best Regards,
Vishwanath
We should update the 3.6.0 (and master) geo-rep docs with these Known
Gotcha's too.
https://github.com/gluster/glusterfs/blob/master/doc/features/geo-replication/distributed-geo-rep.md
Regards and best wishes,
Justin Clift
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
