Bug 1430305 - Fix memory leak in rebalance
Summary: Fix memory leak in rebalance
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-08 10:37 UTC by Susant Kumar Palai
Modified: 2018-03-15 11:16 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 11:16:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Susant Kumar Palai 2017-03-08 10:37:08 UTC
Description of problem:
Fix memory leak in rebalance.

Comment 1 Worker Ant 2017-03-08 10:38:07 UTC
REVIEW: https://review.gluster.org/16870 (cluster/dht: fix memory leaks in rebalance) posted (#1) for review on master by Susant Palai (spalai)

Comment 2 Worker Ant 2017-03-09 06:55:58 UTC
REVIEW: https://review.gluster.org/16870 (cluster/dht: fix memory leaks in rebalance) posted (#2) for review on master by Susant Palai (spalai)

Comment 3 Worker Ant 2017-03-13 10:49:10 UTC
REVIEW: https://review.gluster.org/16870 (cluster/dht: fix memory leaks in rebalance) posted (#3) for review on master by Susant Palai (spalai)

Comment 4 Worker Ant 2017-12-11 04:54:58 UTC
COMMIT: https://review.gluster.org/16870 committed in master by \"Susant Palai\" <spalai> with a commit message- cluster/dht: fix memory leaks in rebalance

From code reading it was found that in gf_defrag_process_dir, GF_FREE
was called directly on dir_dfmeta->equeue leading to leaks of memory for
list of entries read from all the local subvols in case of a failure.

This patch frees the entries read from all the local subvols.

Change-Id: If5e8f557372a8fc2af86628b401e8de1b54986a1
BUG: 1430305
Signed-off-by: Susant Palai <spalai>

Comment 5 Shyamsundar 2018-03-15 11:16:50 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.0.0, please open a new bug report.

glusterfs-4.0.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/


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