Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-10619

Remove `environment_timeout_mode` setting

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 7.0.0
    • Component/s: None
    • Template:
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      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 some number of seconds from when the environment was last used.
      Show
      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 some number of seconds from when the environment was last used.
    • QA Risk Assessment:
      Needs Assessment

      Description

      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).

      The environment_timeout_mode setting was added in PUP-8014, and this ticket is to remove the setting and change the default (and only) behavior so that puppet evicts environments that haven't been used for a certain amount of time.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              josh Josh Cooper
              Reporter:
              maggie Maggie Dreyer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support