Bug 1670415

Summary:	Incremental memory leak of glusterd process in 'gluster volume status all detail
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Andrew Robinson <anrobins>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED ERRATA	QA Contact:	Kshithij Iyer <kiyer>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.3	CC:	amukherj, anrobins, dahorak, kiyer, pasik, rhinduja, rhs-bugs, sheggodu, srakonde, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-1	Doc Type:	Bug Fix
Doc Text:	A small memory leak that occurred when viewing the status of all volumes has been fixed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 12:20:20 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:
Bug Blocks:	1696806

Description Andrew Robinson 2019-01-29 13:55:04 UTC

Description of problem:

For all three nodes in the customer's cluster, the memory usage of the glusterd service grows monotonically. 


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


glusterfs-3.8.4-52.el7rhgs.x86_64


How reproducible:


Steps to Reproduce:
1. Reboot
2. Watch memory usage over days
3.

Actual results:

Memory usage of glusterd climbs until it consumes over 90% of the available memory.


Expected results:

Memory usage of glusterd service remain low and steady


Additional info:

When the customer opened the case, the memory usage by the glusterd service was over 90% of the available memory for each of the three nodes. The customer rebooted each node over the course of several days, which returned memory usage of the glusterd service to less than 3%. The customer has been collecting 'top' outputs every few hours. They show the memory usage steadily climbing since the reboots.

Comment 31 errata-xmlrpc 2019-10-30 12:20:20 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/RHEA-2019:3249