
On Fri, Mar 06, 2015 at 10:58:53AM -0600, Darrell Budic wrote:
I believe the supervdsm leak was fixed, but 3.5.1 versions of vdsmd still leaks slowly, ~300k/hr, yes.
https://bugzilla.redhat.com/show_bug.cgi?id=1158108
On Mar 6, 2015, at 10:23 AM, Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Federico Alberto Sayd <fsayd@uncu.edu.ar> said:
I am experiencing troubles with VDSM memory consuption.
I am running
Engine: ovirt 3.5.1
Nodes:
Centos 6.6 VDSM 4.16.10-8 Libvirt: libvirt-0.10.2-46 Kernel: 2.6.32
When the host boots, memory consuption is normal, but after 2 or 3 days running, VDSM memory consuption grows and it consumes more memory that all vm's running in the host. If I restart the vdsm service, memory consuption normalizes, but then it start growing again.
I have seen some BZ about vdsm and supervdsm about memory leaks, but I don't know if VDSM 4.6.10.8 is still affected by a related bug.
Can't help, but I see the same thing with CentOS 7 nodes and the same version of vdsm. -- Chris Adams <cma@cmadams.net> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I'm afraid that we are yet to find a solution for this issue, which is completly different from the horrible leak of supervdsm < 4.16.7. Could you corroborate the claim of Bug 1147148 - M2Crypto usage in vdsm leaks memory ? Does the leak disappear once you start using plaintext transport? Regards, Dan.