Feature #11834: Migrate our infrastructure to Puppet 4
PuppetDB is regularly unavailable
#2 Updated by intrigeri about 1 year ago
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- QA Check set to Ready for QA
The OOM killer sometimes kills PuppetDB. Last time it happened icinga2 triggered it, an APT regular job +
apt-show-versions + (
check_upgradeable) were running and the PuppetDB java process took total-vm:2777752kB, anon-rss:501188kB, file-rss:0kB, shmem-rss:0kB.
I think this VM simply needs a bit more RAM since we now run PuppetDB on top of everything we used to run before the upgrade to Puppet 4 (and MySQL was replaced with PostgreSQL but I doubt that makes a big difference). So I gave it ~256MiB more RAM (rounding it so it's a multiple of 2048 KiB, our huge pages size). Let's see if it helps.