[Bugs] [Bug 1694612] New: glusterd leaking memory when issued gluster vol status all tasks continuosly
bugzilla at redhat.com
bugzilla at redhat.com
Mon Apr 1 09:05:13 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1694612
Bug ID: 1694612
Summary: glusterd leaking memory when issued gluster vol status
all tasks continuosly
Product: GlusterFS
Version: 5
Hardware: x86_64
OS: Linux
Status: NEW
Component: glusterd
Severity: high
Priority: medium
Assignee: bugs at gluster.org
Reporter: srakonde at redhat.com
CC: amukherj at redhat.com, bmekala at redhat.com,
bugs at gluster.org, nchilaka at redhat.com,
rhs-bugs at redhat.com, sankarshan at redhat.com,
srakonde at redhat.com, storage-qa-internal at redhat.com,
vbellur at redhat.com
Depends On: 1691164
Blocks: 1686255, 1694610
Target Milestone: ---
Classification: Community
Description of problem:
glusterd is leaking memory when issused "gluster vol status tasks" continuosly
for 12 hours. The memory increase is from 250MB to 1.1GB. The increase have
been 750 MB.
Version-Release number of selected component (if applicable):
glusterfs-3.12.2
How reproducible:
1/1
Steps to Reproduce:
1. On a six node cluster with brick-multiplexing enabled
2. Created 150 disperse volumes and 250 replica volumes and started them
3. Taken memory footprint from all the nodes
4. Issued "while true; do gluster volume status all tasks; sleep 2; done" with
a time gap of 2 seconds
Actual results:
Seen a memory increase of glusterd on Node N1 from 260MB to 1.1GB
Expected results:
glusterd memory shouldn't leak
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1686255
[Bug 1686255] glusterd leaking memory when issued gluster vol status all tasks
continuosly
https://bugzilla.redhat.com/show_bug.cgi?id=1691164
[Bug 1691164] glusterd leaking memory when issued gluster vol status all tasks
continuosly
https://bugzilla.redhat.com/show_bug.cgi?id=1694610
[Bug 1694610] glusterd leaking memory when issued gluster vol status all tasks
continuosly
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list