> I haven't seen the patches yet. Failures can happen just at the time of > winding, leading to same failures. It at least needs to have the logic > of picking next_active_child. EC needs to lock+xattrop the bricks to > find bricks with good copies. AFR needs to perform getxattr to find good > copies. Is that really true? I thought they each had a readily-available idea of which children are up or down, which they already use e.g. for reads. _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
