-
Notifications
You must be signed in to change notification settings - Fork 229
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
Add server_multithreaded parameter #720
Add server_multithreaded parameter #720
Conversation
Puppet Server 6.8 has just been released with an experimental new feature. > This release adds a new JRuby pool architecture that maintains a > single JRuby instance through which requests to Puppet Server are run > concurrently. In this mode, the server's memory footprint is > significantly lighter, because it no longer needs to run multiple JRuby > instances. Toggle this behavior by setting the > `jruby-puppet.multithreaded` to `true`. This commit adds support for this new setting.
Looking closer, it would be better to use the puppet-puppet/manifests/server.pp Lines 475 to 483 in 0de3202
The reason is that the version number might be undef (default).
|
I think this is already the case? (Although the module can be a bit confusing to follow). The template function is called from puppetserver.pp and uses
|
You're right on that part. However, maybe it's good to add another condition that if the puppetversion is at least 6.12.0 then the puppetserver version is 6.8.0? |
That could very easily not be true though. The current code is conservative. If your puppet version is 6.X, then so is your puppetserver. Much more than that would probably be too great an assumption. |
yes, in general it's a complicated situation. |
Puppet Server 6.8 has just been released with an experimental new
feature.
This commit adds support for this new setting.