[ovirt-users] Re: Upgraded to oVirt 4.4.9, still have vdsmd memory leak
On Wed, Nov 10, 2021 at 4:46 PM Chris Adams <cma(a)cmadams.net> wrote:
I have seen vdsmd leak memory for years (I've been running oVirt since
version 3.5), but never been able to nail it down. I've upgraded a
cluster to oVirt 4.4.9 (reloading the hosts with CentOS 8-stream), and I
still see it happen. One host in the cluster, which has been up 8 days,
has vdsmd with 4.3 GB resident memory. On a couple of other hosts, it's
around half a gigabyte.
Can you share vdsm logs from the time vdsm started?
We have these logs:
2021-11-14 15:16:32,956+0200 DEBUG (health) [health] Checking health (health:93)
2021-11-14 15:16:32,977+0200 DEBUG (health) [health] Collected 5001
objects (health:101)
2021-11-14 15:16:32,977+0200 DEBUG (health) [health] user=2.46%,
sys=0.74%, rss=108068 kB (-376), threads=47 (health:126)
2021-11-14 15:16:32,977+0200 INFO (health) [health] LVM cache hit
ratio: 97.64% (hits: 5431 misses: 131) (health:131)
They may provide useful info on the leak.
You need to enable DEBUG logs for root logger in /etc/vdsm/logger.conf:
[logger_root]
level=DEBUG
handlers=syslog,logthread
propagate=0
and restart vdsmd service.
Nir