Bug 1642868

Summary:	[GSS][ Memory leak in glusterfs process - possible area affected gf_common_mt_char]
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	nravinas
Component:	glusterfs	Assignee:	Sunny Kumar <sunkumar>
Status:	CLOSED NEXTRELEASE	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.3	CC:	atumball, bkunal, kramdoss, rhs-bugs, sankarshan, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.4.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-14 06:10:13 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:	1647277

Description nravinas 2018-10-25 09:00:02 UTC

Description of problem:

glusterfs process leaking in gf_common_mt_char

Additional info:

glusterfs not leaking any memory

Comment 7 Amar Tumballi 2018-10-29 09:02:19 UTC

> I've seen the number of total_allocs increasing  in gf_common_mt_char area. Side by side comparison between the first and the the last statedumps:

I comment came from the above statement. Total allocs increasing shows that the variable is being used. In general, if there is activity on filesystem, then there will be more increase in 'total_alloc' field. 

But regarding 'size=' value, we need to work. Not every translator or library utilize 'mt_char' to this high number. We will analyze and get back!

Comment 12 Amar Tumballi 2019-03-14 06:10:13 UTC

As per Comment#11, and with LRU limit option, this should go away.