On Wed, Aug 31, 2016 at 8:06 PM, Federico Alberto Sayd <fsayd@uncu.edu.ar> wrote:

Hello Nir:

I followed your instructions , added the config file, restarted vdsm, and today I have the vdsm logs from a host:

https://drive.google.com/file/d/0ByrwZ1AkYuyeR1hmRm90a1R6MEk/view?usp=sharing

Please tell me if you see anything related to the memory issue.

This logs start when vdsm is using 567640 kB (554 MiB) - very unusual.

The memory usage grow by 18 MiB during one day. No garbage collection

issues. This smells like we keep some data forever for no reason.

$ grep rss= vdsm-leak.log | head -n 1

Thread-33::DEBUG::2016-08-30 12:01:43,845::health::122::health::(_check_resources) user=1.73%, sys=1.65%, rss=567640 kB (+44), threads=57

 $ grep rss= vdsm-leak.log | tail -n 1

Thread-33::DEBUG::2016-08-31 13:00:36,913::health::122::health::(_check_resources) user=4.18%, sys=1.87%, rss=586584 kB (+0), threads=52

I would like to see the logs since vdsm was started  - do you have them?

Also, can you describe the workload on this hypervisor?

- how many vms are running at the same time

- how many vms are started and stopped per hour

- using default vdsm.conf? if not, please attach your conf