Bug #33214
potential memory leak in puma
Difficulty:
Triaged:
No
Bugzilla link:
Associated revisions
Refs #33214: Reset puma min threads to default from puppet module
If the default value for foreman_service_puma_threads_min is found,
which is zero, this deletes that value from the answers file. This
allows the new default to be populated from the puppet module. The
new default is to set min threads equal to max threads. If the minimum
is anything other than zero than we can assume the user has customized
the value.
History
#1
Updated by The Foreman Bot over 1 year ago
- Assignee set to Eric Helms
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman/pull/984 added
#2
Updated by The Foreman Bot over 1 year ago
- Pull request https://github.com/theforeman/foreman-installer/pull/713 added
#3
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases 3.1.0 added
#4
Updated by Eric Helms over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|172a16d0a0556b26c2c764f7339f292447cf62f2.
#5
Updated by The Foreman Bot over 1 year ago
- Pull request https://github.com/theforeman/puppet-foreman/pull/985 added
Fixes #33214: Set minimum Puma threads equal to maximum puma threads by default
This has been shown to prevent memory leaks that can appear in Foreman
when running under Puma. This only changes the default to match and
users must still be aware of this potential when changing the tunings.