> 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: Kill
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
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
> 10
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 depend
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 10 resources
Jo
Op dinsdag 6 januari 2015 11:26:40 UTC+1 schreef kaustubh
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
