[Bugs] [Bug 1739337] New: DHT: severe memory leak in dht rename

[bugzilla at redhat.com]

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

            Bug ID: 1739337
           Summary: DHT: severe memory leak in dht rename
           Product: GlusterFS
           Version: 7
            Status: NEW
         Component: distribute
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: nbalacha at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, storage-qa-internal at redhat.com,
                    tdesala at redhat.com
        Depends On: 1722512, 1722698
            Blocks: 1726294
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1722698 +++

+++ This bug was initially created as a clone of Bug #1722512 +++

Description of problem:

The dht rename codepath has a severe leak if it needs to create a linkto file. 
Version-Release number of selected component (if applicable):


How reproducible:
Consistently

Steps to Reproduce:
1. Create a 2x3 distribute replicate volume and fuse mount it.
2. Create 2 directories, dir1 and dir1-new in the root of the volume
3. Find 2 filenames which will hash to different subvols when created in these
directories. For example, in my setup dir1/file-1 and dir1-new/newfile-1 hash
to different subvols. This is necessary as the leak is in the path which
creates a linkto file.
4. Run the following script and watch the memory usage for the mount process
using top.



Actual results:
Memory rises steadily. Statedumps show that the number of active inodes keeps
increasing.

Expected results:
Memory should not increase as there is a single file on the volume.


Additional info:


--- Additional comment from Nithya Balachandran on 2019-06-20 14:10:03 UTC ---

(In reply to Nithya Balachandran from comment #0)
> Description of problem:
> 
> The dht rename codepath has a severe leak if it needs to create a linkto
> file. 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> Consistently
> 
> Steps to Reproduce:
> 1. Create a 2x3 distribute replicate volume and fuse mount it.
> 2. Create 2 directories, dir1 and dir1-new in the root of the volume
> 3. Find 2 filenames which will hash to different subvols when created in
> these directories. For example, in my setup dir1/file-1 and
> dir1-new/newfile-1 hash to different subvols. This is necessary as the leak
> is in the path which creates a linkto file.
> 4. Run the following script and watch the memory usage for the mount process
> using top.
> 
> 
Forgot to mention the script in the description:

while (true); do for in in {1..20000}; do touch /mnt/fuse1/dir1/file-1; mv -f
/mnt/fuse1/dir1/file-1 /mnt/fuse1/dir1-new/newfile-1; done ;rm -rf
/mnt/fuse1/dir1-new/*; done

--- Additional comment from Worker Ant on 2019-06-21 03:38:32 UTC ---

REVIEW: https://review.gluster.org/22912 (cluster/dht:  Fixed a memleak in
dht_rename_cbk) posted (#1) for review on master by N Balachandran

--- Additional comment from Worker Ant on 2019-07-02 11:52:04 UTC ---

REVIEW: https://review.gluster.org/22912 (cluster/dht:  Fixed a memleak in
dht_rename_cbk) merged (#5) on master by N Balachandran


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1722512
[Bug 1722512] DHT: severe memory leak in dht rename
https://bugzilla.redhat.com/show_bug.cgi?id=1722698
[Bug 1722698] DHT: severe memory leak in dht rename
https://bugzilla.redhat.com/show_bug.cgi?id=1726294
[Bug 1726294] DHT: severe memory leak in dht rename
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.