| Release Notes Summary: |
Adds a new setting `environment_timeout_mode` which is controls how the `environment_timeout` setting behaves for values greater than 0 and less than unlimited. By default, which makes it possible to clear short-lived puppet environments from memory, while caching frequently used environments indefinitely. Doing so will reduce Puppet server's memory footprint.
If `environment_timeout` is 0 or unlimited, then there is no change in behavior . Otherwise , environments will be never cached or always cached if the `environment_timeout` is a duration , respectively. For other values such as 3 minutes , environments then the environment will be evicted `environment_timeout` seconds from when 3 minutes after it was
was last used is created .
For the `environment_ttl` setting However , a value of if ` 0 environment_timeout_mode ` will disable caching. This setting can also be is set to` unlimited from_last_used `, which will cache environments until then the server is restarted or told to refresh the cache. All other values environment will result in Puppet server evicting environments that have not been accessed within that ttl be evicted 3 minutes from when it was last used . We recommend either:
You should change this setting once your Puppet deployment is doing non-trivial work. We chose the default value of Setting ` 0 environment_timeout ` because it lets new users update their code without any extra steps, but it lowers the performance of to unlimited and explicitly refreshing your Puppet server as part of your code deployment process .
We recommend Or setting this `environment_timeout` to a number that will keep your most actively used environments cached, but allow testing environments to fall out of the cache and reduce memory usage. A value of 3 minutes (3m) is a reasonable value. This option requires setting `environment_timeout_mode` to `from_last_used`.
Once you set ` environment_ttl environment_timeout ` to a non-zero value, you need to tell Puppet server to read new code from disk using the `environment-cache` API endpoint after you deploy new code. See the docs for the Puppet Server [administrative API](https://puppet.com/docs/puppetserver/latest/admin-api/v1/environment-cache.html).
|
