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

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1683816 (view as bug list)
Environment:
Last Closed: 2019-07-16 04:56:28 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 23040 0 None Merged mgmt/glusterd: Fix a memory leak when peer detach fails 2019-07-16 04:56:27 UTC

Description Vijay Bellur 2019-02-27 21:32:04 UTC 
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-07-15 03:04:29 UTC 
REVIEW: https://review.gluster.org/23040 (mgmt/glusterd: Fix a memory leak when peer detach fails) posted (#1) for review on release-6 by Atin Mukherjee
Comment 2 Worker Ant 2019-07-16 04:56:28 UTC 
REVIEW: https://review.gluster.org/23040 (mgmt/glusterd: Fix a memory leak when peer detach fails) merged (#2) on release-6 by hari gowtham
Note You need to log in before you can comment on or make changes to this bug.