Bug 762519 (GLUSTER-787)

Summary:	Putting a hard limit on glusterfs' memory usage
Product:	[Community] GlusterFS	Reporter:	Krishna Srinivas <krishna>
Component:	core	Assignee:	Anand Avati <aavati>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	amarts, chrisw, 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:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Krishna Srinivas 2010-03-29 21:11:03 UTC

It will be useful to have a configurable number as a hard limit on the memory that can be used by glusterfs process. No doubt memory accounting feature (coming up in 3.1) will be good to fight memory leak problems and track memory usages, by having a hard limit on memory usage on glusterfs we will be able to provision the memory resources.

Comment 1 Amar Tumballi 2010-04-20 08:00:52 UTC

Bug 61 would be contributed for this. If we implement our own memory manager then it should be fine. (Considering GlusterFS uses all the memory which can be purged).

This is a requirement bug, we need to put such requirements in Requirement Database.