Bug 762519 (GLUSTER-787) - Putting a hard limit on glusterfs' memory usage
Summary: Putting a hard limit on glusterfs' memory usage
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-787
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-29 21:11 UTC by Krishna Srinivas
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

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

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

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.
Note You need to log in before you can comment on or make changes to this bug.