Bug 1288019

Summary: Possible memory leak in the tiered daemon
Product: [Community] GlusterFS Reporter: Joseph Elwin Fernandes <josferna>
Component: tieringAssignee: Joseph Elwin Fernandes <josferna>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: asrivast, bugs, dlambrig, josferna, nbalacha, nchilaka, rmekala, sankarshan, smohan
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1285998
: 1288992 (view as bug list) Environment:
Last Closed: 2016-06-16 13:48:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1285998    
Bug Blocks: 1288992    

Comment 1 Vijay Bellur 2015-12-03 10:31:20 UTC
REVIEW: http://review.gluster.org/12867 (tier/dht: Fix mem leak from lookup response dict) posted (#1) for review on master by Joseph Fernandes

Comment 2 Vijay Bellur 2015-12-05 05:44:34 UTC
REVIEW: http://review.gluster.org/12867 (tier/dht: Fix mem leak from lookup response dict) posted (#2) for review on master by Joseph Fernandes

Comment 3 Vijay Bellur 2015-12-07 01:56:03 UTC
COMMIT: http://review.gluster.org/12867 committed in master by Dan Lambright (dlambrig) 
------
commit 02d54bb750c5ad41b81881ce63dd756582aad543
Author: Joseph Fernandes <josferna>
Date:   Thu Dec 3 15:40:16 2015 +0530

    tier/dht: Fix mem leak from lookup response dict
    
    Fixing memory leak from response dict during a parent
    lookup to get the path.
    
    Change-Id: I60c23d0b25e7f763f0e53c40e71ee053aba6d555
    BUG: 1288019
    Signed-off-by: Joseph Fernandes <josferna>
    Reviewed-on: http://review.gluster.org/12867
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Joseph Fernandes
    Tested-by: Joseph Fernandes

Comment 4 Niels de Vos 2016-06-16 13:48:40 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user