Bug 1683816 - Memory leak when peer detach fails
Summary: Memory leak when peer detach fails
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1683815
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-27 21:36 UTC by Vijay Bellur
Modified: 2019-03-04 02:29 UTC (History)
2 users (show)

Fixed In Version:
Clone Of: 1683815
Environment:
Last Closed: 2019-03-04 02:29:46 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 22280 0 None Merged mgmt/glusterd: Fix a memory leak when peer detach fails 2019-03-04 02:29:44 UTC

Description Vijay Bellur 2019-02-27 21:36:35 UTC 
+++ This bug was initially created as a clone of Bug #1683815 +++

Description of problem:

When a peer detach fails, there is a memory leak. By trying to detach my local hostname, I was able to observe a slow increase in resident memory consumption of glusterd.


Version-Release number of selected component (if applicable):


How reproducible:

# gluster peer detach <local-host-name>
Comment 1 Worker Ant 2019-02-27 21:43:29 UTC 
REVIEW: https://review.gluster.org/22280 (mgmt/glusterd: Fix a memory leak when peer detach fails) posted (#1) for review on master by Vijay Bellur
Comment 2 Worker Ant 2019-03-04 02:29:46 UTC 
REVIEW: https://review.gluster.org/22280 (mgmt/glusterd: Fix a memory leak when peer detach fails) merged (#1) on master by Vijay Bellur
Note You need to log in before you can comment on or make changes to this bug.