Bug 1497084

Summary: glusterfs process consume huge memory on both server and client node
Product: [Community] GlusterFS Reporter: hari gowtham <hgowtham>
Component: posixAssignee: hari gowtham <hgowtham>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 3.12CC: amukherj, atumball, bkunal, bmekala, bugs, csaba, hgowtham, mchangir, nbalacha, rgowdapp, rhs-bugs, sankarshan, vbellur, wenshi, wliu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-glusterfs-3.12.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1496379
: 1497108 (view as bug list) Environment:
Last Closed: 2017-10-13 12:47:15 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: 1496379    
Bug Blocks: 1490203, 1497108    

Comment 1 Worker Ant 2017-09-29 08:00:37 UTC
REVIEW: https://review.gluster.org/18410 (Posix: fix additional inode ref) posted (#1) for review on release-3.12 by hari gowtham (hari.gowtham005)

Comment 2 Worker Ant 2017-10-06 06:33:17 UTC
COMMIT: https://review.gluster.org/18410 committed in release-3.12 by jiffin tony Thottan (jthottan) 
------
commit d167bb0871f9fc8b150f026bb0a0710bd203c947
Author: hari gowtham <hgowtham>
Date:   Thu Sep 28 15:43:30 2017 +0530

    Posix: fix additional inode ref
    
            backport of https://review.gluster.org/#/c/18406/
    
    Problem: In the iteration, the inode is being ref-ed twice and
    unref-ed once. this leads to ref leak.
    
    Fix: assign the parent to the inode instead of referencing it.
    
    >BUG: 1496379
    
    Change-Id: Ib154b12d38ad68220f8f5288bbc50081beccc2b9
    BUG: 1497084
    Signed-off-by: hari gowtham <hgowtham>

Comment 3 Jiffin 2017-10-13 12:47:15 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-glusterfs-3.12.2, please open a new bug report.

glusterfs-glusterfs-3.12.2 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/2017-October/032684.html
[2] https://www.gluster.org/pipermail/gluster-users/