Bug 1615443 - Glusterfs client Memory Leak
Summary: Glusterfs client Memory Leak
Keywords:
Status: CLOSED DUPLICATE of bug 1593826
Alias: None
Product: GlusterFS
Classification: Community
Component: libglusterfsclient
Version: 3.12
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-13 15:27 UTC by okane
Modified: 2018-08-14 09:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-14 09:22:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Gluster dumps, version info, gluster info (37.45 KB, application/x-bzip)
2018-08-13 15:27 UTC, okane
no flags Details

Description okane 2018-08-13 15:27:26 UTC
Created attachment 1475607 [details]
Gluster dumps, version info, gluster info

Description of problem:

glusterfs process using too much Memory 


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

glusterfs-3.12  from ovirt-4.2 repositories

rpm -qa | grep gluster
glusterfs-rdma-3.12.11-1.el7.x86_64
glusterfs-client-xlators-3.12.11-1.el7.x86_64
libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.6.x86_64
glusterfs-cli-3.12.11-1.el7.x86_64
python2-gluster-3.12.11-1.el7.x86_64
glusterfs-geo-replication-3.12.11-1.el7.x86_64
glusterfs-server-3.12.11-1.el7.x86_64
glusterfs-fuse-3.12.11-1.el7.x86_64
glusterfs-gnfs-3.12.11-1.el7.x86_64
glusterfs-events-3.12.11-1.el7.x86_64
glusterfs-3.12.11-1.el7.x86_64
vdsm-gluster-4.20.35-1.el7.x86_64
glusterfs-libs-3.12.11-1.el7.x86_64
glusterfs-api-3.12.11-1.el7.x86_64



How reproducible:

This happens on all "non brick" hosts,  3 hosts with bricks + 3 without 
Since Ovirt-4.2.0  most likely since gluster-3.12 , 3.7 (3.9?) was OK.


Steps to Reproduce:
1. Activate Host (mount gluster filesystem) 

2. let run

I realize now I have not simply tried an active host without VMs.. I will test that
and add to this post.


Actual results:

currently using 64GB Ram (and growing ca. 150MB every 1/2 hour. 4 days uptime, maximum 7 VMs on host.

Expected results:

use less memory?


Additional info:

Comment 1 okane 2018-08-14 09:21:27 UTC
Same as Bug 1593826 - Glusterfs being killed due to out of memory situation [NEEDINFO]

Comment 2 okane 2018-08-14 09:22:21 UTC

*** This bug has been marked as a duplicate of bug 1593826 ***


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