Bug 1656682 - brick memory consumed by volume is not getting released even after delete
Summary: brick memory consumed by volume is not getting released even after delete
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On: 1653225 1790336 1811631
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-06 04:30 UTC by Mohit Agrawal
Modified: 2020-03-09 11:41 UTC (History)
9 users (show)

Fixed In Version: glusterfs-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1653225
Environment:
Last Closed: 2019-01-21 03:11:50 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 21810 0 None Abandoned core: Resolve resource leak at the time of stop volume 2019-04-25 19:30:31 UTC
Gluster.org Gerrit 21825 0 None Merged core: Resolve memory leak for brick 2019-01-16 17:32:42 UTC
Gluster.org Gerrit 22058 0 None Merged quotad: fix wrong memory free 2019-01-21 03:11:49 UTC

Comment 1 Worker Ant 2018-12-06 04:47:46 UTC 
REVIEW: https://review.gluster.org/21810 (core: Resolve resource leak at the time of stop volume) posted (#1) for review on master by MOHIT AGRAWAL
Comment 2 Worker Ant 2019-01-16 04:05:08 UTC 
REVIEW: https://review.gluster.org/21825 (core: Resolve memory leak for brick) posted (#4) for review on master by MOHIT AGRAWAL
Comment 3 Worker Ant 2019-01-16 17:32:44 UTC 
REVIEW: https://review.gluster.org/21825 (core: Resolve memory leak for brick) merged (#7) on master by Amar Tumballi
Comment 4 Worker Ant 2019-01-18 03:35:37 UTC 
REVIEW: https://review.gluster.org/22058 (quotad: fix wrong memory free) posted (#1) for review on master by Kinglong Mee
Comment 5 Worker Ant 2019-01-21 03:11:50 UTC 
REVIEW: https://review.gluster.org/22058 (quotad: fix wrong memory free) merged (#2) on master by Amar Tumballi
Comment 6 Shyamsundar 2019-03-25 16:32:33 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.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.