From 270bf0a53abd2c188916d1684af73c09b6bfcb04 Mon Sep 17 00:00:00 2001 From: Nick Walker Date: Wed, 24 Feb 2016 11:47:27 -0800 Subject: [PATCH] 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 --- hieradata/common.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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