<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 11. 03. 2015 16:05, Jeff Darcy
wrote:<br>
</div>
<blockquote
cite="mid:154147812.2639280.1426086311494.JavaMail.zimbra@redhat.com"
type="cite">
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
Could I use cluster.quorum-type and
<meta http-equiv="content-type" content="text/html; charset=utf-8">
cluster.quorum-count?<br>
Would it work with a rep 2+1 setup or would I need a rep 3 setup?<br>
<br>
Kind regards,<br>
Mitja<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</body>
</html>