| Summary: | max_file_size and min_file_size can be set to exceed cache_size | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> |
| Component: | io-cache | Assignee: | krishnan parthasarathi <kparthas> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.1.3 | CC: | amarts, gluster-bugs, nsathyan, vijay |
| 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
Joe Julian
2011-04-02 06:47:23 UTC
max_file_size and min_file_size are bounds on the size of files that the user wants glusterfs to cache. Its a way by which user can selectively turn caching off.
OTOH, cache_size is the amount of memory user sets aside for glusterfs to use for caching files. {min, max}_file_size and cache_size are independent of each other. Closing the bug as invalid.
|