I will test this patch for the issue we've posted couple days ago. Our problem showed itself during self heal and autoheal operations especially when replicating huge number of files sitting in one directory (300K+ files)<br><br><div class="gmail_quote"><div dir="ltr">On Sat, Mar 26, 2016, 15:58 Pranith Kumar Karampuri <<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 03/26/2016 07:20 PM, Lindsay Mathieson wrote:<br>
> On 26/03/2016 11:32 PM, Pranith Kumar Karampuri wrote:<br>
>> Yes, this is a bug we are addressing for 3.7.10. The patch is already<br>
>> merged. <a href="http://review.gluster.org/13564" rel="noreferrer" target="_blank">http://review.gluster.org/13564</a><br>
><br>
><br>
> Excellent, thanks Pranith.<br>
><br>
> Is that the same issue I posted earlier re "gluster volume heal info"<br>
> appearing to block I/O?<br>
><br>
I don't think it is heal info that is blocking I/O. I think it is client<br>
triggering heal and block the fop until heal completes that results in<br>
this pattern. This data-heal disabling should get you out of this problem.<br>
<br>
Pranith<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>