Gluster users - Aug 2017 - filesystem failure on one peer makes volume read only?

.. is this default/desired behaviour?

And is this configurable/controllable behaviour?
I'm thinking - it would be nice not to have whole vol go 
read-only(three peers in cluster) but at the same time have 
gluster alert/highlight the problem to a user/admin.

ver. 3.10.3

thanks.
L.

Could you share the output of 'gluster volume info <volname>' ?

On Tue, Aug 1, 2017 at 5:03 PM, lejeczek <peljasz at yahoo.co.uk> wrote:
> .. is this default/desired behaviour?
>
> And is this configurable/controllable behaviour?
> I'm thinking - it would be nice not to have whole vol go
read-only(three
> peers in cluster) but at the same time have gluster alert/highlight the
> problem to a user/admin.
>
> ver. 3.10.3
>
> thanks.
> L.
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-- 
- Atin (atinm)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170802/6ce96215/attachment.html>