devsnack/control-repo
1
0
Fork 0
Code Releases Activity

Remove max_requests_per_instance since hiera-eyaml is fixed

Browse Source 
Prior to this commit, we mitigated issues with hiera-eyaml causing
a memory leak by setting max_requets_per_instance to 0

After this commit, we go back to the default for
max_requests_per_instance because the hiera-eyaml memory leak
has been resolved for months if you use the newest version
This commit is contained in:
Nick Walker 2016-08-04 15:51:07 -07:00
parent e0d6feea18
commit 5497d199b3
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hieradata/common.yaml
View File

@ -1,5 +1,2 @@
--- ---
message: "This node is using common data" message: "This node is using common data"
#Puppet Server Tuning
puppet_enterprise::master::puppetserver::jruby_max_requests_per_instance: 0