<div dir="ltr"><div>Thank you for reporting this. I had done testing on my local setup and the issue was resolved even with quick-read enabled. Let me test it again.</div><div><br></div><div>Regards,</div><div>Poornima<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 15, 2019 at 12:25 PM Hu Bert <<a href="mailto:revirii@googlemail.com">revirii@googlemail.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">fyi: after setting performance.quick-read to off network traffic<br>
dropped to normal levels, client load/iowait back to normal as well.<br>
<br>
client: <a href="https://abload.de/img/network-client-afterihjqi.png" rel="noreferrer" target="_blank">https://abload.de/img/network-client-afterihjqi.png</a><br>
server: <a href="https://abload.de/img/network-server-afterwdkrl.png" rel="noreferrer" target="_blank">https://abload.de/img/network-server-afterwdkrl.png</a><br>
<br>
Am Mo., 15. Apr. 2019 um 08:33 Uhr schrieb Hu Bert <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>:<br>
><br>
> Good Morning,<br>
><br>
> today i updated my replica 3 setup (debian stretch) from version 5.5<br>
> to 5.6, as i thought the network traffic bug (#1673058) was fixed and<br>
> i could re-activate 'performance.quick-read' again. See release notes:<br>
><br>
> <a href="https://review.gluster.org/#/c/glusterfs/+/22538/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c/glusterfs/+/22538/</a><br>
> <a href="http://git.gluster.org/cgit/glusterfs.git/commit/?id=34a2347780c2429284f57232f3aabb78547a9795" rel="noreferrer" target="_blank">http://git.gluster.org/cgit/glusterfs.git/commit/?id=34a2347780c2429284f57232f3aabb78547a9795</a><br>
><br>
> Upgrade went fine, and then i was watching iowait and network traffic.<br>
> It seems that the network traffic went up after upgrade and<br>
> reactivation of performance.quick-read. Here are some graphs:<br>
><br>
> network client1: <a href="https://abload.de/img/network-clientfwj1m.png" rel="noreferrer" target="_blank">https://abload.de/img/network-clientfwj1m.png</a><br>
> network client2: <a href="https://abload.de/img/network-client2trkow.png" rel="noreferrer" target="_blank">https://abload.de/img/network-client2trkow.png</a><br>
> network server: <a href="https://abload.de/img/network-serverv3jjr.png" rel="noreferrer" target="_blank">https://abload.de/img/network-serverv3jjr.png</a><br>
><br>
> gluster volume info: <a href="https://pastebin.com/ZMuJYXRZ" rel="noreferrer" target="_blank">https://pastebin.com/ZMuJYXRZ</a><br>
><br>
> Just wondering if the network traffic bug really got fixed or if this<br>
> is a new problem. I'll wait a couple of minutes and then deactivate<br>
> performance.quick-read again, just to see if network traffic goes down<br>
> to normal levels.<br>
><br>
><br>
> Best regards,<br>
> Hubert<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>