Bug 762248 (GLUSTER-516) - cache-size should not be hard-coded to 1GB
Summary: cache-size should not be hard-coded to 1GB
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-516
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Harshavardhana
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-04 06:52 UTC by Raghavendra Bhat
Modified: 2015-12-01 16:45 UTC (History)
6 users (show)

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

Attachments (Terms of Use)

Description Raghavendra Bhat 2010-01-04 06:52:06 UTC 
The cache size of io-cache in the volume file generated by glusterfs-volgen is by default set to 1GB. The variable cache_size in the extra/volgen/CreateVolfile.py is set to 1GB. This has to be determined by referring the memory of the system for which the volfile is genetrated......
Comment 1 Anand Avati 2010-01-21 12:45:43 UTC 
PATCH: http://patches.gluster.com/patch/2667 in master (Cache size is now dynamic and is 20% of the total memory on the client side.)
Comment 2 Anand Avati 2010-01-22 10:21:43 UTC 
PATCH: http://patches.gluster.com/patch/2668 in release-2.0 (Cache size is now dynamic and is 20% of the total memory on the client side.)
Comment 3 Anand Avati 2010-01-25 09:32:22 UTC 
PATCH: http://patches.gluster.com/patch/2691 in master (Fix occurence of cache-size being floating point)
Comment 4 Anand Avati 2010-01-25 09:32:34 UTC 
PATCH: http://patches.gluster.com/patch/2692 in release-2.0 (Fix occurence of cache-size being floating point)
Comment 5 Anush Shetty 2010-02-10 13:41:15 UTC 
Verified 2.0.10rc1
Note You need to log in before you can comment on or make changes to this bug.