Bug 1887947 - High Memory Utilization after restart, normally within 5 days. [NEEDINFO]
Summary: High Memory Utilization after restart, normally within 5 days.
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Liran Rotenberg
QA Contact: Lucie Leistnerova
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-13 16:09 UTC by dscott
Modified: 2020-11-16 12:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-16 12:24:15 UTC
oVirt Team: Virt
lrotenbe: needinfo? (dscott)

Attachments (Terms of Use)
Picture of Dashboard (51.34 KB, image/png)
2020-10-13 16:09 UTC, dscott
no flags Details
Tar of /var/log/ovirt-engine/ (3.35 MB, application/gzip)
2020-10-13 16:10 UTC, dscott
no flags Details
Tar of /var/log/vdsm/ (1.52 MB, application/gzip)
2020-10-13 16:13 UTC, dscott
no flags Details
Picture of free command. (22.49 KB, image/png)
2020-10-13 16:15 UTC, dscott
no flags Details

Description dscott 2020-10-13 16:09:22 UTC
Created attachment 1721222 [details]
Picture of Dashboard

Description of problem:
Ovirt server is showing using almost all available physical memory even though running vms which account for less than half of used memory.   Running 6 vms which should be around 128 Gigs of physical memory, showing 220 GBs of used memory after five days.

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

CentOS Linux release 8.2.2004 (Core)
How reproducible:

After restart, server memory usage returns to normal after about three to five days after restart of ovirt server, memory usage spikes to almost all of physical memory.  I have been running this new version for about 6 weeks and has been consistent each time.  I do maintenance every two weeks, with updates to vms and Ovirt.

Steps to Reproduce:
1.  Restart Ovirt-Engine
2.  Memory usage spikes after two days.

Actual results:

Expected results:

Additional info:

Comment 1 dscott 2020-10-13 16:10:48 UTC
Created attachment 1721223 [details]
Tar of /var/log/ovirt-engine/

Comment 2 dscott 2020-10-13 16:13:26 UTC
Created attachment 1721224 [details]
Tar of /var/log/vdsm/

Comment 3 dscott 2020-10-13 16:15:08 UTC
Created attachment 1721225 [details]
Picture of free command.

Comment 4 RHEL Program Management 2020-10-15 13:07:02 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 5 Arik 2020-10-26 12:43:42 UTC
Could be related to memory leak on the engine (bz 1891332)

Comment 6 Liran Rotenberg 2020-10-26 13:27:30 UTC
Could you tell us if it's an Hosted Engine environment (from the logs I figure it doesn't, but still - to be sure).
Also - The free output is from the host? The memory leak sounds in beast.rts-llc.com, which is the host, right?
If so, does restarting the ovirt-engine service "refresh" it, dropping the memory usage? It is unlikely since they are on different machines.
Do you mean restarting something on the host?

Comment 7 Arik 2020-11-16 12:24:15 UTC
We suspect this might be fixed by bz 1891332 but we need to get more information about the environment, specifically whether it's an hosted engine environment.
Feel free to reopen if more data can be provided

Note You need to log in before you can comment on or make changes to this bug.