Bug 762566 (GLUSTER-834) - lru_limit on inodes is hardcoded to 1 million
Summary: lru_limit on inodes is hardcoded to 1 million
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-834
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 08:48 UTC by Raghavendra Bhat
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTA
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2010-04-20 08:48:39 UTC 
The lru_limit on the inodes is hardcoded to 1 million, which leads to high memory usage by the server when a large amount of small files are copied onto the mount point.
Comment 1 Anand Avati 2010-04-22 11:05:05 UTC 
PATCH: http://patches.gluster.com/patch/3152 in master (Do not hardcode the lru_limit on inodes to 1 Million while creating the inode table)
Comment 2 Anand Avati 2010-04-22 11:05:17 UTC 
PATCH: http://patches.gluster.com/patch/3151 in release-3.0 (Do not hardcode the lru_limit on inodes to 1 Million while creating the inode table)
Note You need to log in before you can comment on or make changes to this bug.