Bug 1628219
Summary: | High memory consumption depending on volume bricks count | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Vladislav <vladyslav.reutskyi> |
Component: | libgfapi | Assignee: | bugs <bugs> |
Status: | CLOSED DEFERRED | QA Contact: | bugs <bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | mainline | CC: | atumball, bugs, pasik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-14 10:35:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vladislav
2018-09-12 13:24:04 UTC
Release 3.12 has been EOLd and this bug was still found to be in the NEW state, hence moving the version to mainline, to triage the same and take appropriate actions. Vladislav, Apologies for the delay, but please notice that we do take some space per translator definition. The more number of bricks, the more memory consumed for the same. Yes, it is a known issue for now. Hence we normally claim support upto 128 nodes/bricks only. For using it for larger counts, one need to use higher RAM for sure. FYI - The structure which gets allocated for each xlator is https://github.com/gluster/glusterfs/blob/v6.0/libglusterfs/src/glusterfs/xlator.h#L767..L864 We won't be able to fix it in near future, as most of the logic depends on this structure. Will be marking the issue as DEFERRED. |