[Gluster-devel] GF_FOP_IPC changes

Jeff Darcy jdarcy at redhat.com
Wed Jun 24 14:56:59 UTC 2015

> 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.

More information about the Gluster-devel mailing list