<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">01.08.2018 22:04, Amar Tumballi пишет:<br>
</div>
<blockquote type="cite"
cite="mid:CAHxyDdMAp9OMDpT11k+DEDihLPFyG_hiEjYcy-WF_FA04e7=CQ@mail.gmail.com">
<div dir="ltr">
<div><span>This recently added document talks about some of the
technicalities of the feature:</span>
<div><br>
</div>
<div><a
href="https://docs.gluster.org/en/latest/Administrator%20Guide/Thin-Arbiter-Volumes/"
moz-do-not-send="true">https://docs.gluster.org/en/latest/Administrator%20Guide/Thin-Arbiter-Volumes/</a></div>
<div><br>
</div>
<div>Please go through and see if it answers your questions.</div>
<div><br>
</div>
<div>-Amar</div>
</div>
</div>
</blockquote>
<br>
Hello!<br>
<br>
I have question:<br>
<br>
Manual says:<br>
<br>
<br>
"When one brick is up: Fail FOP with EIO."<br>
<br>
So, if we have 2 nodes with thin arbiter and only one node is up,
i.e. second node is down for some reason, then I/O will be stopped.<br>
Any reasons to have two nodes then?<br>
<br>
Could you tell me is manual right here or it is misprint?<br>
<br>
Thank you!<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAHxyDdMAp9OMDpT11k+DEDihLPFyG_hiEjYcy-WF_FA04e7=CQ@mail.gmail.com">
<div dir="ltr">
<div><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Aug 1, 2018 at 11:09 PM,
wkmail <span dir="ltr"><<a
href="mailto:wkmail@bneit.com" target="_blank"
moz-do-not-send="true">wkmail@bneit.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">I see mentions of thin
arbiter in the 4.x notes and I am intrigued.<br>
<br>
As I understand it, the thin arbiter volume is<br>
<br>
a) receives its data on an async basis (thus it can be
on a slower link). Thus gluster isn't waiting around to
verify if it actually got the data.<br>
<br>
b) is only consulted in situations where Gluster needs
that third vote, otherwise it is not consulted.<br>
<br>
c) Performance should therefore be better because
Gluster is only seriously talking to 2 nodes instead of
3 nodes (as in normal arbiter or rep 3)<br>
<br>
Am I correct?<br>
<br>
If so, is thin arbiter ready for production or at least
use on non-critical workloads?<br>
<br>
How safe is it for VMs images (and/or VMs with
sharding)?<br>
<br>
How much faster is thin arbiter setup over a normal
arbiter given that the normal data only really sees the
metadata?<br>
<br>
In a degraded situation (i.e. loss of one real node),
would having a thin arbiter on a slow link be
problematic until everything is healed and returned to
normal?<br>
<br>
Sincerely,<br>
<br>
-wk<br>
<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org"
target="_blank" moz-do-not-send="true">Gluster-users@gluster.org</a><br>
<a
href="https://lists.gluster.org/mailman/listinfo/gluster-users"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.gluster.org/mail<wbr>man/listinfo/gluster-users</a><br>
<br>
<br>
</blockquote>
</div>
<br>
<br>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Amar Tumballi (amarts)<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<p><br>
</p>
</body>
</html>