Bug 762566 (GLUSTER-834)

Summary:	lru_limit on inodes is hardcoded to 1 million
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	protocol	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	amarts, gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTA	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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)