Bug 765299 (GLUSTER-3567)

Summary:	need more details of memory usage patterns in statedump
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <amarts>
Component:	logging	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Amar Tumballi 2011-09-16 06:13:44 UTC

We are missing details about 'mem-pool' usage, and also, after bringing in variable-sized iobufs bug 762514 is no more valid (ie, we do need passive iobufs to get details of how it was used).

in each type also add how many times each type of variable was allocated. This helps us to understand which of the types can be using 'iobuf' or 'mempool'.

Comment 1 Anand Avati 2011-09-22 08:33:43 UTC

CHANGE: http://review.gluster.com/376 (* iobuf: add variable to keep count of total number of allocations) merged in master by Vijay Bellur (vijay)

Comment 2 Anand Avati 2011-09-23 05:22:59 UTC

CHANGE: http://review.gluster.com/491 (* with this, it helps to find out most of the leaks in the process) merged in master by Vijay Bellur (vijay)