On 20/10/14 21:48, Justin Clift wrote:
----- Original Message -----
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.
Thanks. :)
In the meantime, who is the right person to update our geo-rep
docs to include the gotchas, so people know to avoid them?
I can add do it. I need some time (we have long weekend coming up in
India for Diwali) and some help from Aravinda.
Best Regards,
Vishwanath
+ Justin
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
