Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Kylo Ginsberg assigned an issue to QA Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Kylo Ginsberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Documentation and example changes merged: stable: 26a2830 master: 850d118 and 2afe830 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. I don't really think Henrik's suggestion is the right approach; I agree it's technically accurate, but it's too heavyweight. Users will just want to know how we intended this to be used, not all the ways you could potentially make it limp along. Which is product direction perspective, so we got that from Eric Sorenson in the SoS. Summary is: The default is just there for surprise reduction. If you're reading the docs at all, it's time for you to change the value. Our actual best-practices recommendation is to set unlimited, and ping puppetserver's environment-cache endpoint (or restart apache) when you deploy code. We don't recommend any values other than 0 or unlimited, due to the out-of-sync ruby interpreters issue, but if you really want to, you can do some science and decide whatever you want. We don't recommend setting environment_timeout per-environment; you should manage it globally unless you're really doing something weird. (Eric, is this an accurate summary?) Four remaining tasks on this ticket: Update conf/environment.conf, which wasn't updated at the time of the behavior change. Update defaults.rb description, which has outdated advice. Update docs ticket for updating other relevant pages. I'll do these as soon as I can and then we can get final review on this. Add Comment
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Nicholas Fagerlund can you retarget the PR to stable as this is affects 3.7.5 ? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. On PR to stable is enough, will merge it to master at the same time Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Henrik Lindberg Yeah, totally. I think we'll be releasing 4.0 RCs before 3.7.5. Do two PRs, or expect that we'll be merging up real soon? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Steve Barlow assigned an issue to Nicholas Fagerlund Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Steve Barlow Assignee: NicholasFagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Melissa Stone commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Apologies it's taken me so long to respond to this ticket. Henrik Lindberg are you referring to `conf/environment.conf`? I don't think releng owns that file explicitly. It does get copied into place during packaging (at least for puppet 4 it does), but any changes to the file itself shouldn't impact that. The interesting thing is that I'm not seeing where this is copied into place except in Puppet 4 build automation in the puppet-agent repo Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title
Henrik Lindberg commented on PUP-4094
Re: Default environment_timeout should be 0, not infinity.
How about:
The default value '0' is not optimal for large scale production, but helps keep things from being confusing when you are getting started and making frequent changes to your manifests. When the number of nodes go up and changes are not so frequent you may want to change this parameter to 'unlimited' to make repeated catalog compilations of unchanged code run faster. The trade-off is that you must then manually tell the server to reload the code when changes are made. Values in-between these two ('0' and 'unlimited') means that you make a compromise regarding convenience vs. performance. When setting it to some other value you have to wait for the timeout before changes take effect, but all compilations during that time period will be faster, followed by one slower compilation and then again faster until the next timeout.
If we also want to say something about the gain in performance:
The performance gained by caching depends on the amount of puppet code that is used to compile a catalog. The more code the bigger the reduction in wall clock time spent per compilation. To decide on how much is gained in your configuration, set the timeout to a value longer than it takes to request 2-3 catalogs in sequence. Then compare the compilation times. Under optimal conditions you may observe up to a 60% reduction in compilation time.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Hailee Kenney commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Here is the original commit on stable and here is where it was merged into master Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Sorenson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. We have some very old performance docs here: https://docs.puppetlabs.com/puppet/#tuning-and-scaling There are recent docs that only cover puppet-server here: https://docs.puppetlabs.com/pe/latest/config_puppetserver.html Neither of these are ideal though. There already is long-form documentation that describes the different timeout settings here: http://docs.puppetlabs.com/puppet/3.7/reference/environments_configuring.html#environmenttimeout but I agree it should be punched up in the inline doc for the setting and be made a Release Note headline. I do not think we should emit log messages or warnings. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Hailee Kenney assigned an issue to QA Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Hailee Kenney Status: Readyfor CI Test Assignee: HenrikLindberg QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Hailee Kenney commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. I was able to find the commits but not the PR, there may not have been one. Let me take another look Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Thompson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. [root@j3nxa0euhmqwmrl ~]# cat /etc/puppetlabs/puppet/puppet.conf [agent] server=j3nxa0euhmqwmrl.delivery.puppetlabs.net [root@j3nxa0euhmqwmrl ~]# mkdir -p /etc/puppetlabs/code/environments/production/manifests [root@j3nxa0euhmqwmrl ~]# vi /etc/puppetlabs/code/environments/production/manifests/site.pp [root@j3nxa0euhmqwmrl ~]# puppet master [root@j3nxa0euhmqwmrl ~]# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for j3nxa0euhmqwmrl.delivery.puppetlabs.net Info: Applying configuration version '1425924569' Notice: production Notice: /Stage[main]/Main/Notify[production]/message: defined 'message' as 'production' Notice: Applied catalog in 0.01 seconds [root@j3nxa0euhmqwmrl ~]# vi /etc/puppetlabs/code/environments/production/manifests/site.pp [root@j3nxa0euhmqwmrl ~]# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for j3nxa0euhmqwmrl.delivery.puppetlabs.net Info: Applying configuration version '1425924586' Notice: production updated Notice: /Stage[main]/Main/Notify[production updated]/message: defined 'message' as 'production updated' Notice: Applied catalog in 0.02 seconds [root@j3nxa0euhmqwmrl ~]# puppet master --configprint environment_timeout 0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Eric Sorenson Nicholas Fagerlund and thoughts on deepak's question? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Eric Thompson QA Contact: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Thompson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. PR links? will verify and move to review Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Hailee Kenney commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. (Moving this into testing, but we probably should avoid moving this ticket to resolved until the performance questions above are addressed) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Thompson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. QA risk: medium probability: high severity: low (FR only. tested extensively elsewhere) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Sorenson commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. cc Jorie Tappa and Nicholas Fagerlund for the docs implications. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. FWIW I consider this default easier to explain. Should allow us to reduce docs, and reduce both the number and urgency of situations where a user will need to go to docs. But we need to know some things. How much performance do you gain by turning on caching? Like, back-of-the-envelope calculations are fine, but we at least need some sort of order of magnitude figure we can use to explain why this feature exists at all. What do we really, actually, in real life, recommend that users do? Set to unlimited and make sure your process for deploying new code pings the puppetserver environment cache endpoint? Something else? I badly want to clear away the current thicket of if this then that... maybe non-recommendations about this setting. (And if you're managing your environments as git branches, having a different value per environment seems like an aggravating source of repeated garbage commits, aside from just being difficult to wrap your head around.) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. There was no PR, it was a change of one value, and I did the change and merge to stable and master and pushed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Please target this at 4.0.0 as well, to make sure we have a record that it's in the release. Please edit the description for PUP-2702 with the final resolution of THIS ticket, to make clear that it was reverted before being released. Possibly also change its resolution to wontfix, since otherwise it's deceptive. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Henrik Lindberg Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Nicholas Fagerlund commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Before this ticket can pass review, the /conf/environment.conf file needs an update to reflect the changed default. Our packaging writes this file to the default production environment, to make the environment system more discoverable. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. So updating the environment.conf that is copied to the default production environment. Is that you Melissa Stone that deals with that? Regarding the updated text for the setting, who will wordsmith and update that (Nicholas Fagerlund) ? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. PUP-2702 updated (changed to Won't fix), and this ticket is now marked with dual versions. The maximum performance gain is obtained by not having to reparse and validate all of the content in the environment. The gain depends on the number of modules and the number of manifests - the more modules and manifests the greater the performance gain. As an example; in an environment with 100 modules and 100 defines, creating one instance of each and producing a catalog takes 40% of the time it takes when not caching. The performance gained has a smaller impact on the overall time it takes to complete one agent run since the caching does not affect the time it takes to handle the request, and the time it takes so send a catalog, and process the resulting reports. It does however free up cycles to process additional requests on the same master. The recommendation is really, use 0 (no caching) until you perceive a performance problem (the master is depleted / you cannot get the throughput you want for multiple agents calling in), then either set infinite and use puppet server signal to trigger a cache eviction, or if changes are made more frequently and this is perceived as an irritating extra step, set a shorter cache (minutes) and instead just wait for the environment to time out (if that is perceived as less irritating). For environments where agent requests are infrequent and the manifests are likely to change often (as in a dev scenario), use 0 (no caching). Regarding commits; possibly checkout the branch in the dev environment, then modify the cache value and do not check in this change. It should be possible to use git exclude in the local clone for this too I suppose if it is difficult to remember. (I don't think this is ideal, but better than values flipping back and forth perhaps). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Deepak Giridharagopal commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Would love to get some answers to the above questions before we close this out. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Do we have any specific documentation about performance and tuning? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. Merged to stable and master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Henrik Lindberg Components: DOCS, Server Created: 2015/03/06 11:36 AM Priority: Normal Reporter: Eric Sorenson We've gone back and forth on this a few times ( PUP-2702 , PUP-2639 ) but after running into issues from PS engagements to training to this puppet-dev thread, it seems the best option is actually to default the environment_timeout to 0 (do not cache) and let people tune upwards if they need to. Please set the default to 0 for Puppet 4, and let's update the docs to describe the rationale there.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Kylo Ginsberg Fix Version/s: PUP3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Kylo Ginsberg We'vegonebackandforthonthisafewtimes([PUP-2702],[PUP-2639])butafterrunningintoissuesfromPSengagementstotrainingto[thispuppet-devthread|https://groups.google.com/d/topic/puppet-dev/lnbXyHlviT0/discussion],itseemsthebestoptionisactuallytodefaulttheenvironment_timeoutto0(donotcache)andletpeopletuneupwardsiftheyneedto.Pleasesetthedefaultto0forPuppet 4, 3.7.x and beyondand let'supdatethedocstodescribetherationalethere. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Deepak Giridharagopal commented on PUP-4094 Re: Default environment_timeout should be 0, not infinity. How will we let people know that they need to tune that timeout for perf? Warning on master startup? Warnings in the logs if compiles take N seconds? Should the stock conf file have a comment above the setting discussing performance? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4094) Default environment_timeout should be 0, not infinity.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4094 Default environment_timeout should be 0, not infinity. Change By: Henrik Lindberg Sprint: 2013-08-12Sprint Story Points: 1 Scope Change Reason: Freecapacity Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
