From 5497d199b3c851a317638905e77f44f2fafc64d4 Mon Sep 17 00:00:00 2001
From: Nick Walker <nick.walker@puppetlabs.com>
Date: Thu, 4 Aug 2016 15:51:07 -0700
Subject: [PATCH] Remove max_requests_per_instance since hiera-eyaml is fixed

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
---
 hieradata/common.yaml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/hieradata/common.yaml b/hieradata/common.yaml
index 80bad3a..2baa62b 100644
--- a/hieradata/common.yaml
+++ b/hieradata/common.yaml
@@ -1,5 +1,2 @@
 ---
 message: "This node is using common data"
-
-#Puppet Server Tuning
-puppet_enterprise::master::puppetserver::jruby_max_requests_per_instance: 0