<div dir="ltr"><br><div>Hi Oleksandr,</div><div><br></div><div>You are right. The description should have said it as the limit on the number of inodes in the lru list of the inode cache. I have sent a patch for that.</div><div><a href="http://review.gluster.org/#/c/12242/">http://review.gluster.org/#/c/12242/</a><br></div><div><br></div><div>Regards,</div><div>Raghavendra Bhat</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 24, 2015 at 1:44 PM, Oleksandr Natalenko <span dir="ltr"><<a href="mailto:oleksandr@natalenko.name" target="_blank">oleksandr@natalenko.name</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've checked statedump of volume in question and haven't found lots of iobuf as mentioned in that bugreport.<br>
<br>
However, I've noticed that there are lots of LRU records like this:<br>
<br>
===<br>
[conn.1.bound_xl./bricks/r6sdLV07_vd0_mail/mail.lru.1]<br>
gfid=c4b29310-a19d-451b-8dd1-b3ac2d86b595<br>
nlookup=1<br>
fd-count=0<br>
ref=0<br>
ia_type=1<br>
===<br>
<br>
In fact, there are 16383 of them. I've checked "gluster volume set help" in order to find something LRU-related and have found this:<br>
<br>
===<br>
Option: network.inode-lru-limit<br>
Default Value: 16384<br>
Description: Specifies the maximum megabytes of memory to be used in the inode cache.<br>
===<br>
<br>
Is there error in description stating "maximum megabytes of memory"? Shouldn't it mean "maximum amount of LRU records"? If no, is that true, that inode cache could grow up to 16 GiB for client, and one must lower network.inode-lru-limit value?<br>
<br>
Another thought: we've enabled write-behind, and the default write-behind-window-size value is 1 MiB. So, one may conclude that with lots of small files written, write-behind buffer could grow up to inode-lru-limit×write-behind-window-size=16 GiB? Who could explain that to me?<span class=""><br>
<br>
24.09.2015 10:42, Gabi C write:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
oh, my bad...<br>
coulb be this one?<br>
<br>
</span><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1126831" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1126831</a> [2]<span class=""><br>
Anyway, on ovirt+gluster w I experienced similar behavior...<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a></div></div></blockquote></div><br></div>