[Gluster-devel] inode lru limit

[Raghavendra G]

On Fri, May 30, 2014 at 2:24 PM, Raghavendra Bhat <rabhat at redhat.com> wrote:

>
> Hi,
>
> Currently the lru-limit of the inode table in brick processes is 16384.
> There is a option to configure it to some other value. The protocol/server
> uses inode_lru_limit variable present in its private structure while
> creating the inode table (whose default value is 16384). When the option is
> reconfigured via volume set option the protocol/server's inode_lru_limit
> variable present in its private structure is changed. But the actual size
> of the inode table still remains same as old one. Only when the brick is
> restarted the newly set value comes into picture. Is it ok? Should we
> change the inode table's lru_limit variable also as part of reconfigure? If
> so, then probably we might have to remove the extra inodes present in the
> lru list by calling inode_table_prune.
>

Yes, I think we should change the inode table's lru limit too and call
inode_table_prune. From what I know, I don't think this change would cause
any problems.


>
> Please provide feedback
>
>
> Regards,
> Raghavendra Bhat
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Raghavendra G
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20140602/4cf77d84/attachment.html>