Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration of the number of max requests handled per puppet … #114

Merged
merged 1 commit into from
Apr 29, 2016

Conversation

dfairhurst
Copy link
Contributor

…master process

@dfairhurst
Copy link
Contributor Author

In order to work around https://tickets.puppetlabs.com/browse/PUP-731 we require to be able to customise the number of requests handled per puppet master process invocation (to 1 per process). This change makes the value customisable.
In future, it could make sense to make all these kinds of parameters customisable, but this is the one we require currently.

@dfairhurst dfairhurst force-pushed the feature/config_maxrequests branch from d8eefea to 9776ae8 Compare February 22, 2016 17:42
@dfairhurst
Copy link
Contributor Author

Any chance to get this merged?
Thanks :)

@@ -3,8 +3,8 @@

PassengerUseGlobalQueue On

# Recycle master processes after they service 1000 requests
PassengerMaxRequests 1000
# Recycle master processes after they service <%= @passenger_max_requests %> requests
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would recommend changing to

# Recycle master processes after they service the number of requests specified by PassengerMaxRequests. Default is 1000.

Reasoning being that seeing default when debugging is nice.

@dfairhurst dfairhurst force-pushed the feature/config_maxrequests branch from 9776ae8 to 18787b5 Compare March 7, 2016 16:22
@dfairhurst
Copy link
Contributor Author

Updated as suggested

@ghoneycutt
Copy link
Owner

Apologies, one more thing I had previously forgotten. Each parameter is documented in the README. Could you please document this new parameter in the style of the others.

@dfairhurst dfairhurst force-pushed the feature/config_maxrequests branch from 18787b5 to 3312b02 Compare March 7, 2016 17:37
@dfairhurst
Copy link
Contributor Author

Well spotted - didn't think of that. README now updated

@aschaber1
Copy link
Contributor

@ghoneycutt is there anything else to be done, for this to get merged?

@ghoneycutt ghoneycutt merged commit 94e50e8 into ghoneycutt:master Apr 29, 2016
@ghoneycutt
Copy link
Owner

Thank you!!

Released in v2.18.0

@dfairhurst
Copy link
Contributor Author

Many thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants