ahh i was hoping the puppet master on 3.0 could handle the transport on its 
own, well dealing with 1800+ plus production systems this mechanism could 
be an issue...

On Tuesday, November 27, 2012 9:45:28 AM UTC-5, Matthew Burgess wrote:
>
> On Tue, Nov 27, 2012 at 2:27 PM, Dominic James 
> <domini...@gmail.com<javascript:>> 
> wrote: 
> > Question: on my current puppet setup 2.7.3-0 rhel 6.2 centos - passenger 
> is 
> > used to provide the throughput for the heavy delivery that puppet could 
> not 
> > do by itself, was this fix in version 3.0 puppet? I will be upgrading to 
> 3.0 
> > and will like puppet master to push to multiple of clients without being 
> > clobbered, Can I just use puppet transport agent by itself  instead of 
> using 
> > apache/passenger? 
>
> You'll have to stick with Apache/Passenger for any non-trivial number 
> of nodes.  Webrick (the HTTP server used by the puppetmaster) is 
> single-threaded, so can only handle one client checking in at a time. 
>
> Regards, 
>
> Matt. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Os7DhtsBvEcJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to