Bug 1655201 - dictionary leak at the time of destroying graph
Summary: dictionary leak at the time of destroying graph
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-01 02:07 UTC by Mohit Agrawal
Modified: 2019-06-25 13:38 UTC (History)
2 users (show)

Fixed In Version: glusterfs-6.x
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-25 13:38:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21761 0 None Open core: Resolve dict_leak at the time of destroying graph 2018-12-01 02:18:24 UTC

Description Mohit Agrawal 2018-12-01 02:07:54 UTC
Description of problem:
dictionary leak at the time of destroying graph

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


How reproducible:
Always

Steps to Reproduce:
1.Upgrade the setup from 3.3.1 to 3.4 (for brick multiplex)
2.Stop all the volumes through gluster CLI
3.Stop glusterd
4.Take the dump of /var/lib/glusterd/vols to some other location from all the nodes
5.Move all .rpmsave to volfile like below on all the nodes
 for fl in `find /var/lib/glusterd/vols/ -name "*.rpmsave" ! -name "*tcp-fuse.vol.rpmsave"`
 do
 mv $fl ${fl%.*}
 done;

6.Start glusterd
7.start all the volumes  -- for y in $(gluster v list);do gluster v start $y;done;sleep 60;echo
8.Stop glusterd
9.Move the original vol files from dump to  /var/lib/glusterd/vols/ 
10. Start glusterd 
11. Create/start/stop a single volume in the loop, running brick process has got graph failure during getspec and every xlator has one dictionary leak 

Actual results:

Running brick process is showing memory leak
Expected results:
There should not be memory leak for running brick process during volume create-start-stop.

Additional info:

Comment 1 Worker Ant 2018-12-01 02:18:23 UTC
REVIEW: https://review.gluster.org/21761 (core: Resolve dict_leak at the time of destroying graph) posted (#3) for review on master by MOHIT AGRAWAL


Note You need to log in before you can comment on or make changes to this bug.