[Gluster-devel] [Gluster-users] Replicated volume, one slow brick

[Pranith Kumar Karampuri]

Adding gluster-devel

Raghavendra,
     I remember we discussing about handling these kinds of errors by
ping-timer expiry? I may have missed the final decision on how this was
decided to be handled. So asking you again ;-)

On Thu, Jul 13, 2017 at 2:14 PM, Øyvind Krosby <oyvind at zedge.net> wrote:

> I have been trying to figure out how glusterfs-fuse client will handle it
> when 1 of 3 bricks in a 3-way replica is slower than the others.
>
> It looks like a glusterfs-fuse client will send requests to all 3 bricks
> when accessing a file. But what happens when one of the bricks is not
> responding in time?
>
> We saw an issue when we added external load to the raid volume where the
> brick was located. The disk became 100% busy, and as a result the
> glusterfs-clients hang when they access the volume.
>
> Is there a way to avoid this, and make the clients ask the other two
> bricks for the data when one brick is too slow?
>
> Thanks
>
> Øyvind Krosby
> SRE, Zedge.net
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>



-- 
Pranith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170715/6a3343e1/attachment.html>