Bug 1124451

Summary: vdsm leaks memory
Product: [Retired] oVirt Reporter: Antoni Segura Puimedon <asegurap>
Component: vdsmAssignee: Dima Kuznetsov <dkuznets>
Status: CLOSED DUPLICATE QA Contact: Gil Klein <gklein>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, bazulay, bugs, danken, ecohen, gklein, iheim, mgoldboi, oourfali, ybronhei, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-27 12:33:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Antoni Segura Puimedon 2014-07-29 14:08:58 UTC
Description of problem:
When running vdsm for several days with two VMs (2048Mb RAM each), the amount
of used ram in the host system is 85%. The, as part of the upgrade to 3.5
vdsm was restarted and the host system used memory is now only 32%. This seems
to indicate that vdsm leaks some significant amount of memory.

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


How reproducible:


Steps to Reproduce:
1. Add to a host with 8Gb of RAM two VMs with el6 guests at 2Gb of RAM each
2. do some busy work on the VMs, reboot them, etc
3. Wait about 10-15 days
4. Check the free memory on the host
5. systemctl stop vdsmd
6. systemctl stop supervdsmd
7. systemctl start vdsmd
8. Check now the free memory on the host

Actual results:
The free memory of the host was just 15%
The free memory of the host is 68%


Expected results:
Both levels are really, really close (with some allowed distance for GC)

Additional info:

Comment 1 Dan Kenigsberg 2014-08-27 12:33:04 UTC
Oops, no need to handle this issue twice.

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