Gluster users - Mar 2015 - Quorum setup for 2+1

> I have a follow-up question.
> When a node is disconnected from the rest, the client gets an error
> message "Transport endpoint is not connected" and all access is
> prevented. Write access must not be allowed to such a node. I understand
> that.
> In my case it would be a desired feature to be able to at least read
> files. Is it possible to retain read-only access?
Client-side quorum can do this with the cluster.quorum-reads option, but
it lacks support for arbiters.  The options you've set enforce quorum at
the server side, by killing brick daemons if quorum is lost.  I suppose
it might be possible to add the read-only translator instead of killing
the daemon, but AFAIK there's no plan to add that feature.

On 11. 03. 2015 16:05, Jeff Darcy wrote:
>> I have a follow-up question.
>> When a node is disconnected from the rest, the client gets an error
>> message "Transport endpoint is not connected" and all access
is
>> prevented. Write access must not be allowed to such a node. I
understand
>> that.
>> In my case it would be a desired feature to be able to at least read
>> files. Is it possible to retain read-only access?
> Client-side quorum can do this with the cluster.quorum-reads option, but
> it lacks support for arbiters.  The options you've set enforce quorum
at
> the server side, by killing brick daemons if quorum is lost.  I suppose
> it might be possible to add the read-only translator instead of killing
> the daemon, but AFAIK there's no plan to add that feature.
Could I use cluster.quorum-type and cluster.quorum-count?
Would it work with a rep 2+1 setup or would I need a rep 3 setup?

Kind regards,
Mitja
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150312/113d0359/attachment.html>