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. Unfortunately, in a scenario where you have 4 clients checking-in at the approximately the same time (A,B,C,D), D will wait in the passenger queue, and when A's catalog will be delivered and will start processing, all file resources pointing back to your master will get delayed until D's catalog is ready. To solve this kind of issues, the best way is to dedicate a part of your passenger pool for the puppet file service (use a vhost for instance). File resource are theorically much shorter in time (especially metadata) than compilation requests. Separating both would allow for a smarter queueing at the master level. [snip] -- Brice Figureau My Blog: http://www.masterzen.fr/ -- 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.
