I just found this as well.

If you're working outside of lab environment, increase ReservedCodeCache to 
512m under normal load. If you're working with 6-12 JRuby instances (or a 
max-requests-per-instance value significantly less than 100k), run with a 
ReservedCodeCache of 1G. Twelve or more JRuby instances in a single server 
might require 2G or more.

We need to look into this setting.

On Monday, February 11, 2019 at 7:42:01 AM UTC-6, Mike Sharpton wrote:
>
> Hey all,
>
> We have recently upgraded our environment from Puppetserver 4.2.2 to 
> Puppetserver 6.0.2.  We are running a mix of Puppet 4 and Puppet 6 agents 
> until we can get them all upgraded to 6.  We have around 6000 nodes, and we 
> had 4 Puppetservers, but we added two more due to capacity issues with 
> Puppet 6.  The load is MUCH higher with Puppet 6.  To the question, I am 
> seeing longer and longer agent run times after about two days of the 
> services running.  The only error in the logs that seems to have any 
> relation to this is this string.
>
> 2019-02-11T04:32:28.409-06:00 ERROR [qtp1148783071-4075] [p.r.core] 
> Internal Server Error: java.io.IOException: 
> java.util.concurrent.TimeoutException: Idle timeout expired: 30001/30000 ms
>
>
> After I restart the puppetserver service, this goes away for about two 
> days.  I think Puppetserver is dying a slow death under this load (load 
> average of around 5-6).  We are running Puppetserver on vm's that are 
> 10X8GB and using 6 Jruby workers per Puppetserver and a 4GB heap.  I have 
> not seen any OOM exceptions and the process never crashes.  Has anyone else 
> seen anything like this?  I did some Googling and didn't find a ton of 
> relevant stuff.  Perhaps we need to upgrade to the latest version to see if 
> this helps?  Even more capacity?  Seems silly.  Thanks in advance!
>
> Mike
>

-- 
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/c96d091a-43b0-4a30-b275-b70ca63ed4b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to