Startup Configuration
There are a number of startup settings that you can configure, including JAVA_HEAP_SIZE
.
Meridian startup scripts load ${OPENNMS_HOME}/etc/opennms.conf
early in their startup, if that file exists.
No opennms.conf
exists in the default RPM/DEB installation, but ${OPENNMS_HOME}/etc/examples
includes a sample file that you can use as a starting point.
Variable | Description | Default | Behavior |
---|---|---|---|
|
Specifies the maximum amount of memory the JVM should use. You may want to increase this value if you experience long response times, frequent garbage collection that takes a lot of time, or see alarms that should have been cleared automatically still listed as alarms. See performance tuning on Discourse for more information. |
2048 |
Units are in megabytes.
Suffix |
|
Specifies the initial amount of memory the JVM should use.
Effectively sets a minimum memory value when used in conjunction with |
null |
Units are in megabytes.
Suffix |
|
Additional options to pass to Java when starting Meridian. |
Appended to other JVM startup flags. |
|
|
You may want to change these values if you end up with too many "files open exceptions" in Meridian. See How to investigate file descriptor issues on Discourse for more information. |
20480 |
Passed to |
|
Defines the size limit for each Java thread in the JVM. |
8192 |
Units are in kilobytes.
Passed to |