Bug 765227 (GLUSTER-3495) - Please remove the 6GB cache-size limit
Summary: Please remove the 6GB cache-size limit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3495
Product: GlusterFS
Classification: Community
Component: core
Version: 3.3-beta
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-30 14:36 UTC by Jacob Shucart
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: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Jacob Shucart 2011-08-30 14:36:11 UTC
I spoke with Harsha and AB and it seems like there is no real reason to have this limit.  Now that systems frequently have much larger amounts of memory, please remove this 6GB limit or increase it to 32GB.  People can decide for themselves whether they have enough memory to create such a large cache.  Thank you.

Comment 1 Amar Tumballi 2011-09-13 02:03:11 UTC
Kaushal,

To solve this I am thinking of below limits. Let the option not have any hardcoded max limit on it. But when one sets a value, we can check '/proc/meminfo' (in #ifdef LINUX_HOST_OS) and get value of 'MemTotal:' and then allow upto 50% of the value as higher limit.

In terms of code, changes would be:

* API to get the total available ram size.

* changes in io-cache:
  - remove the max-limit
  - check if the limit is more than 50% of total available size in init()/reconfigure().

Comment 2 Jacob Shucart 2011-09-13 12:56:45 UTC
I don't think we should put a 50% limit.  If someone has 96GB of RAM in their system and they want to use more than 48 I see no problem with that.  I have a specific user who wants to set it to 64GB in a system with 96GB, and I doubt that would cause an issue with their system, would it?

Comment 3 Anand Avati 2011-09-29 13:39:52 UTC
CHANGE: http://review.gluster.com/409 (Does the following:) merged in master by Vijay Bellur (vijay)


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