Bug 1527551 - [RHEL 6] high memory usage by glusterd on executing gluster volume set operations
Summary: [RHEL 6] high memory usage by glusterd on executing gluster volume set operat...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Atin Mukherjee
QA Contact: Ambarish
URL:
Whiteboard:
Depends On: 1522833 1526363
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-19 13:40 UTC by Atin Mukherjee
Modified: 2021-03-11 16:43 UTC (History)
13 users (show)

Fixed In Version: glusterfs-3.8.4-52.1
Doc Type: Bug Fix
Doc Text:
Executing gluster volume set operations on volumes from gluster CLI caused a significant memory leak in glusterd process. The memory leak issues have been fixed in this release.
Clone Of: 1526363
Environment:
Last Closed: 2018-01-11 02:52:28 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0084 0 normal SHIPPED_LIVE glusterfs bug fix update 2018-01-11 07:52:11 UTC

Comment 6 Ambarish 2017-12-29 09:22:43 UTC 
I don't see a significant increase in memory consumption by glusterd during repeated vol set operations on RHEL 6 nodes as well.

** BEFORE VOL SET,POST CREATION OF 300 VOLUMES** : 

[root@gqas001 ~]# ps aux|grep sbin/glusterd
root     13643  1.1  0.1 590480 110624 ?        Ssl  Dec28   0:48 /usr/sbin/glusterd --pid-file=/var/run/glusterd.pid

**AFTER 300*3 VOL SET COMMANDS *

[root@gqas001 ~]# ps aux|grep sbin/glusterd
root     13643 12.8  0.1 656020 115732 ?        Ssl  Dec28  22:07 /usr/sbin/glusterd --pid-file=/var/run/glusterd.pid


glustershd is still a problem , but that's being addressed by https://bugzilla.redhat.com/show_bug.cgi?id=1529501

I am moving this to Verified , since the delta is reasonable and is far better than what it was in 3.3.1 Gold.
Comment 9 errata-xmlrpc 2018-01-11 02:52:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0084
Note You need to log in before you can comment on or make changes to this bug.