Bug 1655201
| Summary: | dictionary leak at the time of destroying graph | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Mohit Agrawal <moagrawa> |
| Component: | core | Assignee: | Mohit Agrawal <moagrawa> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | atumball, bugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-6.x | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-25 13:38:21 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: | |||
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 |
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: