diff options
| author | mail_redacted_for_web | 2016-02-24 11:47:27 -0800 |
|---|---|---|
| committer | mail_redacted_for_web | 2016-02-24 11:47:27 -0800 |
| commit | 270bf0a53abd2c188916d1684af73c09b6bfcb04 (patch) | |
| tree | 6310ea123fe0c598e2fbb457cda6aa8827e651f0 | |
| parent | 36737bb5fc3458126463ead25c2852fbd58ac7fc (diff) | |
| download | control-repo-template-270bf0a53abd2c188916d1684af73c09b6bfcb04.tar.bz2 | |
Disable max-requests-per-instance to mitigate hiera-eyaml mem leak
Hiera-eyaml currently causes a memory leak in puppetsever when
max-requests-per-instnace is enabled. So, defaulting to disabling
max-requests-per-instance.
https://tickets.puppetlabs.com/browse/SERVER-1154
https://github.com/TomPoulton/hiera-eyaml/issues/163
| -rw-r--r-- | hieradata/common.yaml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hieradata/common.yaml b/hieradata/common.yaml index 8be38fe..291ad51 100644 --- a/hieradata/common.yaml +++ b/hieradata/common.yaml @@ -2,7 +2,7 @@ message: "This node is using common data" #Puppet Server Tuning -puppet_enterprise::master::puppetserver::jruby_max_requests_per_instance: 10000 +puppet_enterprise::master::puppetserver::jruby_max_requests_per_instance: 0 #Enable code manager puppet_enterprise::profile::master::code_manager_auto_configure: true puppet_enterprise::master::code_manager::authenticate_webhook: false |