Bug 1527551

Summary:	[RHEL 6] high memory usage by glusterd on executing gluster volume set operations
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Ambarish <asoman>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	rhgs-3.3	CC:	amukherj, asoman, asriram, bmekala, moagrawa, rabhat, rcyriac, rhinduja, rhs-bugs, sheggodu, srmukher, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.3.1 Async
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:	1526363	Environment:
Last Closed:	2018-01-11 02:52:28 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:	1522833, 1526363
Bug Blocks:

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