Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1154624

Summary: vdsm process leaking memory
Product: [Retired] oVirt Reporter: Daniel Helgenberger <daniel.helgenberger>
Component: vdsmAssignee: Saggi Mizrahi <smizrahi>
Status: CLOSED DUPLICATE QA Contact: Gil Klein <gklein>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5CC: bazulay, bugs, daniel.helgenberger, ecohen, gklein, iheim, lsurette, mgoldboi, oourfali, rbalakri, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-28 09:50:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
pmap -x of VDSM, run every 1h none

Description Daniel Helgenberger 2014-10-20 11:03:23 UTC 
Created attachment 948502 [details]
pmap -x of VDSM, run every 1h

Description of problem:
The vdsm process on my hosts is leaking memory at a rate of about 15MiB/h.

Version-Release number of selected component (if applicable):
2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

vdsm-python-zombiereaper-4.16.7-1.gitdb83943.el6.noarch
vdsm-xmlrpc-4.16.7-1.gitdb83943.el6.noarch
vdsm-4.16.7-1.gitdb83943.el6.x86_64
vdsm-python-4.16.7-1.gitdb83943.el6.noarch
vdsm-yajsonrpc-4.16.7-1.gitdb83943.el6.noarch
vdsm-jsonrpc-4.16.7-1.gitdb83943.el6.noarch
vdsm-cli-4.16.7-1.gitdb83943.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Start vdsmd
2. Observe RSS size
3. wait some time
4. Observe RSS size

Actual results:
VDSMd RSS size is growing. In my setup 15MiB/h

Expected results:
VDSM RSS size not growing

Additional info:
This might be related to BZ1147148 / M2Crypto
Comment 1 Barak 2014-10-21 12:29:10 UTC 
- is your system a stand alone (vdsm only ... no engine) ?
- did you actually run VMs ?
- did you install the host using host deploy or manually ?
Comment 2 Daniel Helgenberger 2014-10-21 14:19:56 UTC 
- is your system a stand alone (vdsm only ... no engine) ?
oVirt Hosted Engine

- did you actually run VMs ?
VMs are running. I can test without them, though

- did you install the host using host deploy or manually ?
Host was installed initially using hosted-engine-deply and updated using 'reinstall' from within engine
Comment 3 Daniel Helgenberger 2014-10-23 09:01:53 UTC 
Running no VMs on the hosts is yielding the same process growth rate (= has no effect):

Do 23. Okt 00:00:45 CEST 2014
total kB         6683896 1130508 1120352
Do 23. Okt 01:00:45 CEST 2014
total kB         6683896 1142944 1132788
Do 23. Okt 02:00:45 CEST 2014
total kB         6683896 1155300 1145144
Do 23. Okt 03:00:45 CEST 2014
total kB         6704388 1167580 1157424
Do 23. Okt 04:00:45 CEST 2014
total kB         6694140 1179896 1169740
Do 23. Okt 05:00:45 CEST 2014
total kB         6683896 1192072 1181916
Do 23. Okt 06:00:45 CEST 2014
total kB         6749432 1204312 1194156
Do 23. Okt 07:00:45 CEST 2014
total kB         6749432 1216724 1206568
Do 23. Okt 08:00:45 CEST 2014
total kB         6749432 1229020 1218864
Do 23. Okt 09:00:45 CEST 2014
total kB         6749432 1241508 1231352
Do 23. Okt 10:00:45 CEST 2014
total kB         6749432 1253844 1243688
Comment 4 Daniel Helgenberger 2014-10-28 09:50:04 UTC 

*** This bug has been marked as a duplicate of bug 1147148 ***