Issue #15420 has been updated by Patrick Carlisle. Status changed from Unreviewed to Investigating
It appears to me from reading the code that the master respects the configtimeout option, which defaults to 120 seconds. The documentation on that option implies it is only for the agent, but all http connections share the same code. Would it be practical to use that? If so, we could change the docs for that option. If not, we should probably separate them completely. While playing with this I also discovered that on ruby 1.8.7 net::http does not respect timeout during the ssl handshake. ---------------------------------------- Bug #15420: puppet master resource starvation on http report url timeouts instead of failures https://projects.puppetlabs.com/issues/15420#change-67310 Author: Ramon Alteren Status: Investigating Priority: Normal Assignee: Category: reports Target version: Affected Puppet version: 2.7.13 Keywords: Branch: We recently had an issue with puppetdashboard that caused it to timeout instead of fail / succeed. Since the default http timeout in ruby is set to 60 seconds, the puppetmaster process is busy for the entire catalog-handling + and additional 60secs to wait on report http post timeout. This causes severe resource starvation on the master resulting in failed puppet runs for _all_ nodes It would make sense to add a timeout parameter for http reports or in the long run split off http reporting into a separate thread/process on the master... -- 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.
