Bug 1496379 - glusterfs process consume huge memory on both server and client node
Summary: glusterfs process consume huge memory on both server and client node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: posix
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: hari gowtham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1490203 1497084 1497108
TreeView+ depends on / blocked
 
Reported: 2017-09-27 08:47 UTC by hari gowtham
Modified: 2017-12-08 17:42 UTC (History)
15 users (show)

Fixed In Version: glusterfs-3.13.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1490203
: 1497084 (view as bug list)
Environment:
Last Closed: 2017-12-08 17:42:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Worker Ant 2017-09-27 08:51:04 UTC 
REVIEW: https://review.gluster.org/18406 (Posix: fix additional inode ref) posted (#1) for review on master by hari gowtham (hari.gowtham005)
Comment 2 Worker Ant 2017-09-28 10:16:41 UTC 
REVIEW: https://review.gluster.org/18406 (Posix: fix additional inode ref) posted (#2) for review on master by hari gowtham (hari.gowtham005)
Comment 5 hari gowtham 2017-09-29 05:44:45 UTC 
Description of problem:
Client is using FUSE to access gluster Tier volume. When they executed their batch application to write files to this Tier volume, over 30G memory will be consumed on both server and client node. 

Version-Release number of selected component (if applicable):
master (current 3.12)

How reproducible:
Every time 

Steps to Reproduce:
1. create a volume and mount it
2. write files to the volume.
3. while writes are happening attach a tier.
4. after a few minutes of writes. delete the all files
5. check the statedump for client and server. they will have a difference. 

Actual results:
Memory exhaustion will happen

Expected results:
No memory exhaustion should happen
Comment 6 Worker Ant 2017-09-29 06:36:53 UTC 
COMMIT: https://review.gluster.org/18406 committed in master by Raghavendra G (rgowdapp) 
------
commit e4784f26bf9739853379ec13d0f921ddfb954475
Author: hari gowtham <hgowtham>
Date:   Thu Sep 28 15:43:30 2017 +0530

    Posix: fix additional inode ref
    
    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.
    
    Change-Id: Ib154b12d38ad68220f8f5288bbc50081beccc2b9
    BUG: 1496379
    Signed-off-by: hari gowtham <hgowtham>
Comment 7 Shyamsundar 2017-12-08 17:42:08 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.13.0, please open a new bug report.

glusterfs-3.13.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/announce/2017-December/000087.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.