[Gluster-devel] GF_FOP_IPC changes
Pranith Kumar Karampuri
pkarampu at redhat.com
Wed Jun 24 15:14:46 UTC 2015
On 06/24/2015 08:26 PM, Jeff Darcy wrote:
>> 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.
It knows which bricks are up/down. But they may not be the latest. Will
that matter?
Pranith
>
>
More information about the Gluster-devel
mailing list