<div dir="ltr"><div>Hi Strahil,</div><div><br></div><div>Thanks for the tip about choose-local. Am I right in thinking that it only applies to reads on a GlusterFS server node itself, and not on GlusterFS clients?</div><div><br></div><div>If so then perhaps the effect could be expanded to clients by using NFS to access the GlusterFS server instead of the GlusterFS native client.</div><div><br></div><div>BTW, under normal circumstances when the client checks all bricks, does that include checking an arbiter? Or are arbiters not checked?</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 25 Apr 2020 at 19:41, Strahil Nikolov <<a href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On April 25, 2020 9:00:30 AM GMT+03:00, David Cunningham <<a href="mailto:dcunningham@voisonics.com" target="_blank">dcunningham@voisonics.com</a>> wrote:<br>
>Hi Ravi,<br>
><br>
>Thank you for the reply, and yes they are replica volumes. Is it<br>
>possible<br>
>to improve performance by the client only accessing its configured<br>
>server<br>
>for reads, or would the difference be negligible?<br>
><br>
><br>
>On Fri, 24 Apr 2020 at 18:46, Ravishankar N <<a href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>><br>
>wrote:<br>
><br>
>><br>
>> On 24/04/20 11:42 am, David Cunningham wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> My understanding is that GlusterFS checks with all nodes when<br>
>performing a<br>
>> read. Is it possible to just get the data from the node directly<br>
>being<br>
>> accessed (in our case using the GlusterFS client), without consulting<br>
>with<br>
>> the other nodes?<br>
>><br>
>> Our application requires the GFS file to be available, but it's<br>
>actually<br>
>> not critical if we end up with an old version of the file in the case<br>
>of a<br>
>> server down or net-split etc. Significantly improved read performance<br>
>would<br>
>> be desirable instead.<br>
>><br>
>> I assume you are talking about replica volumes, in which case the<br>
>read<br>
>> does happen from only one of the replica bricks. The client only<br>
>sends<br>
>> lookups to all the bricks to figure out which are the good copies.<br>
>Post<br>
>> that, the reads themselves are served from only one of the good<br>
>copies.<br>
>><br>
>> -Ravi<br>
>><br>
>><br>
>> Thanks in advance for any help.<br>
>><br>
>> --<br>
>> David Cunningham, Voisonics Limited<br>
>> <a href="http://voisonics.com/" rel="noreferrer" target="_blank">http://voisonics.com/</a><br>
>> USA: +1 213 221 1092<br>
>> New Zealand: +64 (0)28 2558 3782<br>
>><br>
>> ________<br>
>><br>
>><br>
>><br>
>> Community Meeting Calendar:<br>
>><br>
>> Schedule -<br>
>> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
>> Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
>><br>
>> Gluster-users mailing<br>
>listGluster-users@gluster.orghttps://<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>><br>
>><br>
<br>
Hey David,<br>
There is a cluster.choose-local (I think it was 'cluster , but I could be wrong) option that allows a node to read locally - in my case I'm using it cause my network is slower than my NVMe so reads over the network are slow.<br>
<br>
Best Regards,<br>
Strahil Nikolov<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>David Cunningham, Voisonics Limited<br><a href="http://voisonics.com/" target="_blank">http://voisonics.com/</a><br>USA: +1 213 221 1092<br>New Zealand: +64 (0)28 2558 3782</div></div></div></div></div></div></div></div></div></div></div>