On 11/29/2012 8:44 AM, GordonJB wrote:
storeconfigs is not enabled on the master.
Just realised I probably should have mentioned versions, I'm on master &
nodes 3.0.1 and dashboard is 1.2.12.
I'm betting that most of your servers are checking in at the same time.
Half of the clients make it through. The other half are waiting while
the Puppet master processes fight for resources with Puppet dashboard
which is busy trying to process the reports that have just come in. At
some point the clients give up.
I like these settings for Passenger 3.x
PassengerMaxPoolSize <number of cores * 2>
PassengerMinInstances 1
PassengerMaxRequests 10000
PassengerStatThrottleRate 30
If you're running 12 Puppet master Rack processes then you should have
at least 6 cores, though keep in mind that Puppet dashboard will need a
core or two as well.
The other limiting factor is RAM. If you've experienced lockups, you
might have too many Rack processes which clock in around 150-250M.
The simplest solution is to make sure your clients check ins are spaced
somewhat evenly apart. However with only 30 clients as long as you don't
globally restart the Puppet client on all machines and have a four core
Puppet master you'd likely be fine.
Also set a cron to run the cleanup scripts against the Puppet dashboard
db daily and delete reports or it'll grow quite large.
Ramin
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
