Hello, in the meantime I've added RAM and extended the heap to 2GB. But still I'm getting crashes of PuppetDB. Last time it was the kernel OOM that killed the java process as I saw in /var/log/messages kernel: Out of memory: Kill process 10146 (java) score 158 or sacrifice child kernel: Killed process 10146, UID 498, (java) total-vm:3649108kB, anon-rss:1821580kB, file-rss:72kB
Does this mean I need to add additional heap space and/or RAM? I'm looking at the dashboard and it's as if the heap slowly increases. Right after startup it's 3 of 400 MB, after a day or 1 I'm over 1 GB .... I have no clue in how to find out what exactly is wrong. When I was running PuppetDB 1.6 I could do with 256MB heap space. Does anyone have an idea how to investigate what's wrong? Best Regards, Jo Op dinsdag 6 januari 2015 14:15:30 UTC+1 schreef kaustubh chaudhari: > > For your Reference : > https://docs.puppetlabs.com/puppetdb/2.2/scaling_recommendations.html#initial-memory-recommendations > > -Kaustubh > > On Tuesday, January 6, 2015 8:14:24 AM UTC-5, kaustubh chaudhari wrote: >> >> Hey, >> >> I noticed that you mentioned you are managing 850 nodes and you are using >> 1024MB for java Heap size. As per the recommendation this seems to be OK. >> >> As per the documentation you need to allocate 128MB + 1MB per node ie: >> 128 + 850 = 978 MB is the minimum requirement. Also the scaling depends on >> the how many catalog runs etc. >> >> Performance might be the issue if you have less CPU cores. >> >> So what you are seeing about memory close to 1024MB is Ok, my >> recommendation is to increase it further to stay away from OOM. >> >> -HTH >> Kaustubh >> >> >> >> >> On Tuesday, January 6, 2015 7:19:56 AM UTC-5, jdt wrote: >>> >>> I'm running java-1.7.0-openjdk-1.7.0.65-2.5.1.2.el6_5 that might not be >>> the very latest. I'm on CentOS 6.5 >>> >>> The heap space usage is pretty close to 1GB,when I look at it via the >>> PuppetDB dashboard. I'm managing over 100000 resources >>> >>> Jo >>> >>> >>> Op dinsdag 6 januari 2015 11:26:40 UTC+1 schreef kaustubh chaudhari: >>>> >>>> Did you upgrade the openjdk to the latest ? >>>> >>>> i did the same upgrade. for me things are running smooth. >>>> >>>> -Kaustubh >>>> >>>> On Tuesday, January 6, 2015 2:35:04 AM UTC-5, jdt wrote: >>>>> >>>>> Hello, >>>>> >>>>> I recently upgraded to PuppetDB2.2.0 from 1.6.3 >>>>> When I was running PuppetDB1.6.3 with Puppet 3.4.3 I could do with >>>>> 256Mb of heap space for PuppetDB after the upgrade I've increased first >>>>> to >>>>> 512Mb and 768Mb but I kept getting Out of Memory, so now I've increased >>>>> it >>>>> to 1Gb. >>>>> When looking at the dashboard it seems like memory is slowly >>>>> increasing, >>>>> I'm running Puppet v3.6.2 with PuppetDB2.2.0 on CentOS6.x with Ruby >>>>> 1.8.7. I have about 850 active puppet agents >>>>> >>>>> Has anyone seen the same behaviour? How can I find out what exactly is >>>>> wrong if anything? >>>>> >>>>> Best Regards, >>>>> Jo >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/eea02d76-507a-441b-a431-bd9080e8559d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
