[Bugs] [Bug 1628219] High memory consumption depending on volume bricks count

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1628219

Amar Tumballi <atumball at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|unspecified                 |high
             Status|NEW                         |CLOSED
                 CC|                            |atumball at redhat.com
         Resolution|---                         |DEFERRED
           Severity|unspecified                 |high
        Last Closed|                            |2019-06-14 10:35:29



--- Comment #2 from Amar Tumballi <atumball at redhat.com> ---
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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.