On 1/30/20 2:47 PM, Martin Perina wrote:
On Thu, Jan 30, 2020 at 2:45 PM Chris Adams <cma(a)cmadams.net
Once upon a time, Sandro Bonazzola <sbonazzo(a)redhat.com
> Il giorno lun 16 dic 2019 alle ore 19:41 Chris Adams
<cma(a)cmadams.net <mailto:email@example.com>> ha
> > I've seen vdsmd leak memory (RSS increasing) for a while
(brought it up
> > on the lists and opened a BZ ticket), and never gotten
> > diagnosing or resolving it. I reinstalled my dev setup Friday
> > up-to-date CentOS 7 (minimal install) and oVirt 4.3, with a hosted
> > engine on iSCSI (multipath if it matters).
> Adding +Martin Perina <mperina(a)redhat.com
<mailto:firstname.lastname@example.org>> and +Milan Zamazal
> <mzamazal(a)redhat.com <mailto:email@example.com>> for awareness
Is there any possibility of someone helping me look at this? I'm
the issue much worse with 4.3 - a cluster I updated to 4.3.7 two
ago has a host (where the hosted engine was running) where vdsmd
over 20G RSS.
Marcin, any suggestions how to investigate it?
Python mem profiling is hard... I
already tackled the VDSM memory leak
VDSM was growing, but not at a scale that Chris is describing. Tried out
but got to a point, where enforcing periodic garbage collecting made
VDSM mem usage
constant, so the conclusion made there was no mem leaks.
Chris, if I understood you correctly, a single machine suffices to
reproduce your issue?
One that acts as a host with hosted engine on it + iscsi storage?
If so, maybe I/you could construct a VM with a reproducible environment
Having something like this would make investigating this issue much more
Chris Adams <cma(a)cmadams.net <mailto:firstname.lastname@example.org>>
Manager, Software Engineering
Red Hat Czech s.r.o.