Bug 1369331 - Memory leak with a replica 3 arbiter 1 configuration
Summary: Memory leak with a replica 3 arbiter 1 configuration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: arbiter
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1369748 1369752
TreeView+ depends on / blocked
 
Reported: 2016-08-23 07:31 UTC by Ravishankar N
Modified: 2017-03-27 18:19 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.9.0
Clone Of:
: 1369748 1369752 (view as bug list)
Environment:
Last Closed: 2017-03-27 18:19:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ravishankar N 2016-08-23 07:31:40 UTC
Description of problem:

http://www.gluster.org/pipermail/gluster-users/2016-August/028126.html

From the stateump provided by Benjamin:

[features/arbiter.vol1-arbiter - usage-type gf_arbiter_mt_iatt memusage]
size=1103760672
num_allocs=9855006
max_size=1103760672
max_num_allocs=9855006
total_allocs=9855006

Comment 1 Worker Ant 2016-08-23 07:34:48 UTC
REVIEW: http://review.gluster.org/15289 (arbiter: Fix memleak in arbiter_forget) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Worker Ant 2016-08-23 17:31:53 UTC
REVIEW: http://review.gluster.org/15289 (arbiter: Fix memleak in arbiter_inode ctx) posted (#2) for review on master by Ravishankar N (ravishankar)

Comment 3 Worker Ant 2016-08-24 02:10:24 UTC
COMMIT: http://review.gluster.org/15289 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 4aa52061a51b97c4f865b402f977b3b43f5471a7
Author: Ravishankar N <ravishankar>
Date:   Tue Aug 23 12:51:57 2016 +0530

    arbiter: Fix memleak in arbiter_inode ctx
    
    Problem:
    The iattbuf ptr stored in arbiter's inode context was not freed during inode
    forget.
    
    Fix:
    Change it to a statically allocated value so that we don't have to deal
    with allocating/freeing it.
    
    Change-Id: Id1b73b8aee1fb5c4174d0734bd20e168432b1abd
    BUG: 1369331
    Reported-by: Benjamin Edgar <benedgar8>
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/15289
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 4 Shyamsundar 2017-03-27 18:19:27 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.

glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.