[Bugs] [Bug 1420571] New: Massive xlator_t leak in graph-switch code

[bugzilla at redhat.com]

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

            Bug ID: 1420571
           Summary: Massive xlator_t leak in graph-switch code
           Product: GlusterFS
           Version: mainline
         Component: core
          Assignee: bugs at gluster.org
          Reporter: jdarcy at redhat.com
                CC: bugs at gluster.org



In high-scale tests (hundreds of volumes with four bricks each) it became
apparent that a frightening percentage of our memory in a brick process was
being consumed by xlator_t structures, in numbers exactly proportional to the
*square* of how many volumes we had.  This happens because every volume
creation would result in a FETCHSPEC request being sent and acted upon for
every previously existing volume.  Since the teardown of the graph used to
process each such request wasn't freeing the xlator_t, this would leak every
xlator_t in every temporary graph on every iteration.

The fix, quite simply, is to take advantage of the painstaking work already
done and *actually free* the structure at the right point.

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