On 29/07/13 12:20, Matthew Burgess wrote:
On 29 July 2013 11:52, Jonathan Gazeley
<jonathan.gaze...@bristol.ac.uk
<mailto:jonathan.gaze...@bristol.ac.uk>> wrote:
I'd like to know how to increase the number of simultaneous runs
the puppetmaster can handle because as we keep increasing the
number of nodes in our network we wil surely run into problems.
Hi Jonathan,
If you're not already running your puppetmaster behind
Apache/Passenger then that would be my initial recommendation.
Webrick, puppet's default http server, can only handle 1 agent checkin
at a time and is usually the 1st culprit in scaling issues. Although
it's always worth ensuring PuppetDB/Postgres are operating
efficiently, my understanding is that Puppet -> PuppetDB
communications are asynchronous, so even if they do take a long time,
it shouldn't be affecting your master -> agent interactions.
Kind Regards,
Matt.
Hi Matt,
Thanks for your response. We are indeed running puppetmaster behind
Apache/Passenger. We can handle more than one agent checkin at once, but
triggering more than a few simultaneously will usually result in
timeouts or spurious errors such as the agents claiming that one of
their classes does not exist.
Thanks,
Jonathan
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
