Okay, so it turns out that puppet server 2.0.0 has a default setting for 
the maximum number of ruby threads that is equal to 2 more than the number 
of CPUs in the system.  SInce I'm running on a system with 48 CPUs 
[threads], puppetserver was starting 50 ruby threads, and quickly overran 
the [also default] 2GB heap size.  I have reset the `max-active-instances` 
parameter to 4, and we'll see how that goes.  I need to figure out how long 
an average catalog will take to generate and work out how many ruby threads 
I need to support 250 nodes doing updates every 10 minutes.

- Johnson

On Monday, May 4, 2015 at 12:25:24 PM UTC-7, Johnson Earls wrote:
>
> Hey folks,
>
> I just wanted to find out if anyone has been successful in setting up 
> puppet server 2.0.0 and running it?
>
> I ask because, in my test deployment with the puppet server and one puppet 
> agent, the puppet server crashed after less than 5 hours with an out of 
> memory error.  I've just restarted it about an hour ago, so I'll see if it 
> repeats itself.
>
> I'm running Oracle Linux 6.6 on an Oracle SUN X4-2 server with 256GB RAM - 
> not trying it in VMs yet.  The only things I could think of that are 
> out-of-the-ordinary in my setup are (a) agents are updating every 10 
> minutes, (b) the agent on the non-server test node does not have a server 
> role configured, so it's just generating a fail() message in the site.pp 
> manifest, and (c) the puppet server is running the openjdk version of java 
> 1.7.
>
> If anyone has any advice about running (or not running) puppet server 
> 2.0.0 in a production deployment, I'd love to hear it.
>
> Thanks in advance,
> - Johnson
>

-- 
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/95156128-f0b2-4d0e-8fa9-87e95c0a06d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to