Hi Morten,
I replaced the cache.py with the patched one from 1.1.5. It does seems to be stable now.. I will see if it's ok tomorrow.
Kind regards,
René.
-----Oorspronkelijk bericht----- Van: Morten Brekkevold morten.brekkevold@uninett.no Verzonden: dinsdag 17 september 2019 08:01 Aan: René Romijn Rene.Romijn@tabsholland.nl CC: 'nav-users@uninett.no' nav-users@uninett.no Onderwerp: Re: Upgrade Debian to Buster and NAV to 4.9.8
On Tue, 17 Sep 2019 05:54:18 +0000 René Romijn Rene.Romijn@tabsholland.nl wrote:
This is indeed what i am saying 😊
After a couple of day's the memory consumption from the carbon proces is sky high, it seems like carbon cannot write back the cache or something like that.
If your VM has been provisioned with enough RAM, that could actually be the case, depending on your data influx rate...
For now i have reverted tot he older installation and i will try to investigate whats going on.
If the carbon-cache-bug I pointed out in their issue tracker can cause something like this, then that might be your culprit. In that case, I would advise you to either stay on Debian Stretch or patch carbon-cache yourself (until the Debian team patches the Buster package).
Knowing this, I would *not* deploy on Buster until I had a proper fix.
-- sincerely, Morten Brekkevold Uninett