On Mon, Mar 23, 2015 at 04:00:14PM -0400, John Taylor wrote:
Chris Adams <cma(a)cmadams.net> writes:
> Once upon a time, Sven Kieske <s.kieske(a)mittwald.de> said:
>> On 13/03/15 12:29, Kapetanakis Giannis wrote:
>> > We also face this problem since 3.5 in two different installations...
>> > Hope it's fixed soon
>>
>> Nothing will get fixed if no one bothers to
>> open BZs and send relevants log files to help
>> track down the problems.
>
> There's already an open BZ:
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=1158108
>
> I'm not sure if that is exactly the same problem I'm seeing or not; my
> vdsm process seems to be growing faster (RSS grew 952K in a 5 minute
> period just now; VSZ didn't change).
For those following this I've added a comment on the bz [1], although in
my case the memory leak is, like Chris Adams, a lot more than the 300KiB/h
in the original bug report by Daniel Helgenberger .
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1158108
That's interesting (and worrying).
Could you check your suggestion by editing sampling.py so that
_get_interfaces_and_samples() returns the empty dict immediately?
Would this make the leak disappear?
Dan.