Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 844324

Summary:	core: possible memory leak
Product:	[Community] GlusterFS	Reporter:	Saurabh <saujain>
Component:	core	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	pre-release	CC:	amarts, gluster-bugs, junaid, mzywusko, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0qa4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 10:11:32 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:

Description Saurabh 2012-07-30 09:58:52 UTC

Description of problem:

[root@gqac026 ~]# gluster volume info test1
 
Volume Name: test1
Type: Distributed-Replicate
Volume ID: ae4f5ddc-dcf1-4298-b705-c71e81a5b12f
Status: Started
Number of Bricks: 6 x 2 = 12
Transport-type: tcp
Bricks:
Brick1: 10.16.157.81:/home/test1-dr
Brick2: 10.16.157.75:/home/test1-dr2
Brick3: 10.16.157.78:/home/test1-d2r
Brick4: 10.16.157.21:/home/test1-d2r2
Brick5: 10.16.157.81:/home/test1-d3r
Brick6: 10.16.157.75:/home/test1-d3r2
Brick7: 10.16.157.78:/home/test1-d4r
Brick8: 10.16.157.21:/home/test1-d4r2
Brick9: 10.16.157.81:/home/test1-d5r
Brick10: 10.16.157.75:/home/test1-d5r2
Brick11: 10.16.157.78:/home/test1-d6r
Brick12: 10.16.157.21:/home/test1-d6r2
Options Reconfigured:
features.quota: on
geo-replication.indexing: on
[root@gqac026 ~]# 


logs for /var/log/glusterfs/mnt-gluster-object-AUTH_test1.log:-
[2012-07-30 09:45:16.452042] E [mem-pool.c:503:mem_put] (-->/usr/lib64/glusterfs/3.3.0/xlator/cluster/replicate.so(afr_setxattr_wind_cbk+0xe6) [0x7fda9a15a406] (-->/usr/lib64/glusterfs/3.3.0/xlator/cluster/replicate.so(afr_setxattr_unwind+0xe3) [0x7fda9a157ef3] (-->/usr/lib64/glusterfs/3.3.0/xlator/cluster/distribute.so(dht_err_cbk+0xfd) [0x7fda99f0f5fd]))) 1-mem-pool: invalid argument
[2012-07-30 09:45:16.469633] E [mem-pool.c:503:mem_put] (-->/usr/lib64/glusterfs/3.3.0/xlator/cluster/replicate.so(afr_setxattr_wind_cbk+0xe6) [0x7fda9a15a406] (-->/usr/lib64/glusterfs/3.3.0/xlator/cluster/replicate.so(afr_setxattr_unwind+0xe3) [0x7fda9a157ef3] (-->/usr/lib64/glusterfs/3.3.0/xlator/cluster/distribute.so(dht_err_cbk+0xfd) [0x7fda99f0f5fd]))) 1-mem-pool: invalid argument

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

[root@gqac026 ~]# glusterfs -V
glusterfs 3.3.0 built on Jul 19 2012 14:08:45
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.

How reproducible:
happening for the first time, on all nodes of the cluster

Steps to Reproduce:
1. volume as mentioned above.
2. start gluster-object servers
3. enable geo-rep indexing and quota
4. create 40000 container, start requests on them
  
Actual results:
seems to be a mem-leak as per the logs

Expected results:


Additional info:

Comment 1 Amar Tumballi 2012-07-30 10:16:14 UTC

do you have the core file? want to analyze it.

Comment 2 Amar Tumballi 2012-11-21 09:56:28 UTC

not seen this in recent times, please let us know if its an issue still. Otherwise would close it as INSUFFICIENT_DATA.

Comment 3 Raghavendra Bhat 2012-12-04 10:11:32 UTC

some leak fixes have gone in to master, assume those would have fixed it by now.