Once upon a time, Dan Kenigsberg <danken(a)redhat.com> said:
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?
So, to confirm, it looks like to do that, the steps would be:
- In the [vars] section of /etc/vdsm/vdsm.conf, set "ssl = false".
- Restart the vdsmd service.
Is that all that is needed? Is it safe to restart vdsmd on a node with
active VMs?
--
Chris Adams <cma(a)cmadams.net>