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

GC config hardcoded in template #28

Open
siliconalchemy opened this issue Jun 1, 2023 · 4 comments
Open

GC config hardcoded in template #28

siliconalchemy opened this issue Jun 1, 2023 · 4 comments

Comments

@siliconalchemy
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 7.20
  • Ruby: 2.7.6p219
  • Distribution: Ubuntu 22.04
  • Module version: 0.3.0

How to reproduce (e.g Puppet code you use)

class { 'opensearch':
}

What are you seeing

JVM GC settings are hardcoded in template templates/jvm.options.epp

What behaviour did you expect instead

It would be very helpful to be configurable through manifests, in particular Xloggc, NumberOfGCLogFiles and GCLogFileSize. Otherwise the GC logs can fill up the filesystem considerably, even in small installs, with Gbs of largely useless logs.

@siliconalchemy
Copy link
Author

It's this line that is used now instead of NumberOfGCLogFiles and GCLogFileSize:

# JDK 9+ GC logging
9-:-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/opensearch/gc.log:utctime,pid,tags:filecount=2,filesize=16m

crazymind1337 added a commit to syseleven/puppet-opensearch that referenced this issue Feb 6, 2024
crazymind1337 added a commit to syseleven/puppet-opensearch that referenced this issue Feb 6, 2024
crazymind1337 added a commit to syseleven/puppet-opensearch that referenced this issue Feb 6, 2024
bastelfreak added a commit that referenced this issue Feb 6, 2024
(#28) - add missing parts former commit
@crazymind1337
Copy link
Member

@siliconalchemy are you satisfied with the change I have made? If so you can close this issue.

@siliconalchemy
Copy link
Author

Thankyou! Are all the entries for different jdk versions still applicable to opensearch? It's quite confusing to a non-java user that's just looking to use opensearch. I note that even in the reference the default settings aren't mentioned, or any clear note on how to change the default logging - for a non-java user it's relatively hard work to find out how to turn off GBs worth of useless (to a user) logs.

@crazymind1337
Copy link
Member

Well I just used the default config from the package. I think they added this kind of config to ensure opensearch works, if somebody decided to use another jdk for some reason.

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

No branches or pull requests

3 participants