Bug 1611110 - Glusterd memory leaking in gf_gld_mt_linebuf
Summary: Glusterd memory leaking in gf_gld_mt_linebuf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 4.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On: 1575539 1580352
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-02 05:15 UTC by Kotresh HR
Modified: 2018-08-29 12:45 UTC (History)
12 users (show)

Fixed In Version: glusterfs-4.1.3
Clone Of: 1580352
Environment:
Last Closed: 2018-08-29 12:45:07 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3465301 0 None None None 2018-08-02 05:15:42 UTC

Comment 1 Kotresh HR 2018-08-02 05:18:08 UTC 
Description:

glusterd leaks memory when geo-replication status command is run continuously.
Comment 2 Worker Ant 2018-08-02 05:57:03 UTC 
REVIEW: https://review.gluster.org/20610 (glusterd: memory leak in geo-rep status) posted (#1) for review on release-4.1 by Kotresh HR
Comment 3 Worker Ant 2018-08-16 14:28:38 UTC 
COMMIT: https://review.gluster.org/20610 committed in release-4.1 by "Kotresh HR" <khiremat> with a commit message- glusterd: memory leak in geo-rep status

Backport of:
 > BUG: 1580352
 > Change-Id: I9648e73090f5a2edbac663a6fb49acdb702cdc49
 > Signed-off-by: Sanju Rakonde <srakonde>

fixes: bz#1611110
Change-Id: I9648e73090f5a2edbac663a6fb49acdb702cdc49
Signed-off-by: Sanju Rakonde <srakonde>
Comment 4 Shyamsundar 2018-08-29 12:45: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-4.1.3, please open a new bug report.

glusterfs-4.1.3 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/2018-August/000111.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.