Issue #15420 has been updated by Ramon Alteren.
I think it doesn't make sense to share the configtimeout option. We'd want the report timeout to be short so any problem there results in a very quick "report upload fail" We'd want a much more lax configtimeout for the agent, since we run the agent on the master as well, sharing the timeout between the two would mean that the agent ont the master would have the same timeout for http connects as the reporting engine. That doesn't sound like a good idea at all.... ---------------------------------------- Bug #15420: puppet master resource starvation on http report url timeouts instead of failures https://projects.puppetlabs.com/issues/15420#change-67338 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.
