Bug 1667779 - glusterd leaks about 1GB memory per day on single machine of storage pool
Summary: glusterd leaks about 1GB memory per day on single machine of storage pool
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On: 1667169
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-21 03:29 UTC by Mohit Agrawal
Modified: 2019-03-25 16:33 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1667169
Environment:
Last Closed: 2019-01-21 11:11:34 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 22064 0 None Merged glusterd: Resolve memory leak in get-state command 2019-01-21 11:11:33 UTC

Comment 2 Worker Ant 2019-01-21 11:11:34 UTC 
REVIEW: https://review.gluster.org/22064 (glusterd: Resolve memory leak in get-state command) merged (#6) on master by Atin Mukherjee
Comment 3 Shyamsundar 2019-03-25 16:33:07 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.