Disable max-requests-per-instance to mitigate hiera-eyaml mem leak #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 voxpupuli/hiera-eyaml#163
glarizza
pushed a commit
that referenced
this pull request
Feb 25, 2016
…e_setting Disable max-requests-per-instance to mitigate hiera-eyaml mem leak
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
voxpupuli/hiera-eyaml#163