| Summary: | Please remove the 6GB cache-size limit | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Jacob Shucart <jacob> |
| Component: | core | Assignee: | Kaushal <kaushal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3-beta | CC: | amarts, gluster-bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| 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
Jacob Shucart
2011-08-30 14:36: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(). 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? CHANGE: http://review.gluster.com/409 (Does the following:) merged in master by Vijay Bellur (vijay) |