Jira (PUP-10619) Remove `environment_timeout` setting in favor of `environment_ttl`

[Maggie Dreyer (Jira)]

Maggie Dreyer created an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl` Issue Type: Task Assignee: Unassigned Created: 2020/08/14 11:17 AM Priority: Normal Reporter: Maggie Dreyer The environment_timeout setting is a less-than-ideal way of dealing with environment purging, because it doesn't take into account the actual usage patterns for any given environment, and forces the user to make a call on whether to accept longer load times (timeout of 0), inconsistent state between JRubies (a timeout between 0 and unlimited), and high memory usage (unlimited timeout). So instead, we want to implement and environment_ttl setting that will purge environments when they haven't been accessed for a certain amount of time, see PUP-8014. When this is in, we want to remove the environment_timeout setting in favor of the smarter purging mode. Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Maggie Dreyer (Jira)]

Maggie Dreyer updated an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Maggie Dreyer Labels: platform_7

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Josh Cooper Team: Froyo

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Josh Cooper Team: Froyo Coremunity

Add Comment

[Josh Cooper (Jira)]

Josh Cooper assigned an issue to Josh Cooper

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Josh Cooper Assignee: Josh Cooper

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Josh Cooper Fix Version/s: PUP 7.0.0

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-10619

Re: Remove `environment_timeout` setting in favor of `environment_ttl` Keep the old environment_timeout setting, emit a warning, and have it set environment_ttl.

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-10619

Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Josh Cooper Sprint: Platform Core KANBAN

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl` Change By: Josh Cooper

The {{environment_timeout}} setting is a less-than-ideal way of dealing with environment purging, because it doesn't take into account the actual usage patterns for any given environment, and forces the user to make a call on whether to accept longer load times (timeout of 0), inconsistent state between JRubies (a timeout between 0 and unlimited), and high memory usage (unlimited timeout).

So instead, we want to implement and The {{ environment_ttl environment_timeout_mode }} setting was added in PUP-8014, and this ticket is to change the remove the setting and change the default (and only) behavior so that will purge puppet evicts environments when they that haven't been accessed used for a certain amount of time , see PUP-8014 . When this is in, we want to remove the {{environment_timeout}} setting in favor of the smarter purging mode.

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-10619 Remove `environment_timeout` setting in favor of `environment_ttl`

Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Puppet no longer supports environment timeouts based on when the environment was created, as a result the {{environment_timeout_mode}} setting has been removed. In Puppet 7, the {{environment_timeout}} setting is always interpreted as "0" (never cache), "unlimited" (always cache), or a a value relative to when the environment was last used.

Add Comment