Issue #5953 has been updated by Eric Shamow.
Just ran into this with a customer. Symptoms were slow client runs, no visible errors on Puppetmaster side other than client executions expiring, and lots of Passenger timeouts. Client had ~ 450 nodes checking in at the time of the problem. Only two master processes were running....a quick poke in the pe-httpd confs showed PassengerMaxPoolSize set to 2. This was something I ordinarily had set higher in F/OSS configs, and based on master CPU and RAM it was safe to up this to around 8, which resolved the problem. We could probably use, if not more sane defaults in the package, at least a sizing guide for us and for customers with regard to Passenger config. ---------------------------------------- Bug #5953: Improvements to httpd/passenger config https://projects.puppetlabs.com/issues/5953 Author: eric sorenson Status: Accepted Priority: Normal Assignee: Category: Target version: post-GA Keywords: Branch: Affected PE version: (from email, with a little post-facto tweaking) PE drops config files for passenger in /etc/puppetlabs/httpd/conf.d -- these could use a little tweaking: 10-pe-httpd-passenger.load - loadmodule directive 11-pe-httpd-passenger.conf - sets PassengerRoot and PassengerRuby - why are these two split up? passenger-extra.conf - current just has PassengerMaxPoolSize - I tune this based on memory/cpu cores available and add PassengerHighPerformance, PassengerUseGlobalQueue, PassengerMaxRequests and PassengerPoolIdleTime parameters per jmccune's suggestion; perhaps those parameters ought to be included by default. Also, shouldn't this one be a numbered config file like the first two, so it's guaranteed to load before any virtualhost definitions that use it? puppetmaster.conf - by local convention (and this is purely my preference but I think its beneficial) I suffix configfiles that define a listener with the port they bind to, so this would become passenger_8140.conf -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
