JVM Configuration

Data Node

The JVM configuration for the Data Node is stored in:

  • /etc/logserver/jvm.options - main JVM options file

  • /etc/logserver/jvm.options.d/ - directory for additional JVM option files

By default, Data Node tells the JVM to use a heap with a minimum (Xms) and maximum (Xmx) size of 1 GB. When moving to production, it is important to configure heap size to ensure that Data Node has enough heap available.

Heap Sizing

To change the heap size, edit /etc/logserver/jvm.options and set the -Xms and -Xmx values:

-Xms16g
-Xmx16g

Guidelines:

  • Always set -Xms equal to -Xmx to prevent heap resizing at runtime.

  • Do not exceed 31GB to maintain JVM compressed ordinary object pointers (compressed oops), which significantly improve memory efficiency.

  • As a general rule, allocate no more than half of the available system RAM to the JVM heap, leaving the rest for the operating system and file system cache.

After changing the heap size, restart the Data Node service:

systemctl restart logserver

Additional JVM Options

You can place additional JVM configuration files in /etc/logserver/jvm.options.d/. Each file should contain one JVM option per line. This is used, for example, for SSO configuration (see Authentication and Directory Integration).

Network Probe

The JVM configuration for the Network Probe is stored in:

  • /etc/logserver-probe/jvm.options

To apply TLS-related Java security properties, make sure the following definition is present in /etc/logserver-probe/jvm.options:

-Djava.security.properties=/etc/logserver-probe/java.properties

After changing JVM options, restart the Network Probe service:

systemctl restart logserver-probe