On Sunday, March 3, 2013 3:53:29 AM UTC-6, Brice Figureau wrote: > > On 01/03/13 22:24, r.yeo wrote: > > Passenger settings are currently - > > > > PassengerHighPerformance on > > PassengerUseGlobalQueue on > > > > PassengerMaxPoolSize 3 > > This parameter means you're allowing only 3 puppet clients to talk to > your master at any time. > > I can understand why you've set it up this low, because essentially a > puppet master is a CPU bound process, so your master host might not be > able to compile more than 3 catalog at one time. > > I think you're missing the key characteristics of the problem:
1. The error does not occur during catalog compilation. That's fast (enough) in all the failure cases. Instead, the failure occurs during retrieval of 'sourced' files. 2. On failing nodes, *all* the file retrievals exhibit the same delay. 3. File retrieval delays are always within a few milliseconds of 75s. If the problem arose from congestion at the master then the delays would be less consistent from file to file and from run to run, and they would sometimes affect catalog compilation. John -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
