Graylog Data Node heap size configuration

Graylog Central (peer support)
1

I’m testing installing graylog-datanode on RHEL 9 system and I noticed that in the docs, it mentions to specify in the datanode.conf a value for opensearch_heap. However, after install, I noticed the graylog-datanode systemd service is using a JVM options file located in /etc/graylog/datanode/jvm.options. This file appears to be generated upon the package installation.

graylog-datanode-7.0.6-1.x86_64 : Graylog data node
Repo        : graylog
Matched from:
Filename    : /etc/graylog/datanode/jvm.options

The file defaults to 1g for both min and max heap. The resulting process is running as below. My question is am I supposed to update the file so that it reflects the larger heap size that I want for graylog-datanode?

graylog+   24176       1  5 12:51 ?        00:00:16 /usr/share/graylog-datanode/jvm/bin/java -Dlog4j.configurationFile=file:///etc/graylog/datanode/log4j2.xml -Xms1g -Xmx1g -XX:+UseG1GC -XX:-OmitStackTraceInFastThrow -XX:+UnlockExperimentalVMOptions -Djdk.tls.acknowledgeCloseNotify=true -jar /usr/share/graylog-datanode/graylog-datanode.jar datanode -f /etc/graylog/datanode/datanode.conf
2

Datanode service is just the wrapper, it isn’t doing that much work so often 1gb of heap is more than enough, then the opensearch service running “inside” datanode is what needs the big heap, its doing the heavy lifting.

3

Just to clarify, the 1g heap for service is not limiting the heap for the opensearch process? I had assumed that it would the graylog-datanode.jar that encapsulates OpenSearch.

4

Ya they run separately, so one heap does not effect the other.