Bug 1753880 - Set the default lru-limit in fuse to a smaller number
Summary: Set the default lru-limit in fuse to a smaller number
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 07:02 UTC by Nithya Balachandran
Modified: 2019-09-24 13:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-24 13:22:52 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23461 0 None Merged glusterfs/fuse: Reduce the default lru-limit value 2019-09-24 13:22:51 UTC

Description Nithya Balachandran 2019-09-20 07:02:20 UTC
Description of problem:

the lru-limit option in the fuse xlator is currently set to 128K. This is still a a very large number of inodes to have hanging around in memory.

I propose reducing this to a smaller default value.
 
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-09-20 08:09:19 UTC
REVIEW: https://review.gluster.org/23461 (glusterfs/fuse: Reduce the default lru-limit value) posted (#1) for review on master by N Balachandran

Comment 2 Worker Ant 2019-09-24 13:22:52 UTC
REVIEW: https://review.gluster.org/23461 (glusterfs/fuse: Reduce the default lru-limit value) merged (#3) on master by N Balachandran


Note You need to log in before you can comment on or make changes to this bug.