[Bugs] [Bug 1425623] New: Free all xlator specific resources when xlator->fini() gets called

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 21 22:52:15 UTC 2017


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

            Bug ID: 1425623
           Summary: Free all xlator specific resources when xlator->fini()
                    gets called
           Product: GlusterFS
           Version: mainline
         Component: core
          Keywords: Tracking, Triaged
          Assignee: ndevos at redhat.com
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org
            Blocks: 1397177



Description of problem:
With gfapi there are (long-living) processes that handle constructing and
tearing down of xlator graphs. One major contributor to this is the calling of
glfs_init() and glfs_fini() to (re)mount a Gluster volume. Each cycle all the
xlators for the volume are initialized, and many do not free all their
resources (memory allocation, threads, open files, ...) in the fini() call.

Additional info:
There is a tool "gfapi-load-volfile" that can be used to check the resource
leaks in single xlators. It currently is available from
https://github.com/nixpanic/gluster-debug and it may be moved to
https://github.com/gluster/gluster-debug

This bug will be used to track progress of single bugs that fix resource leaks
in specific xlators.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1397177
[Bug 1397177] memory leak when using libgfapi
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Bj7YdAcBuz&a=cc_unsubscribe


More information about the Bugs mailing list