vi /etc/bp2/bpocore/bpocore.conf
Avoiding memory issues by increasing JVM
By default, the bpocore Java virtual machine (JVM) settings are set to a relatively small value in order to allow running on development and proof of concept systems. When running at scale, JVM requires some tuning. This section describes the steps to configure the JVM.
Ciena recommends you increase the JVM heap size for bpocore to about a third of the host RAM memory size up to 60 GB.
To increase the JVM heap size to 16 GB for bpocore, you can pass command-line arguments to the bpocore java process using a configuration file. The java.opts configuration key takes an array of argument strings. This increase is appropriate for a host with 48 GB of RAM.
-
For a single or multi-host Blue Planet solution, edit this file using a text editor:
-
Add the following line into the file:
java.opts = ["-Xmx16G", "-Xms16G"]
-
For a multi-host Blue Planet server, create this file on one host and copy it to the other hosts using the
bp2-site sync-site-config
command. -
Use
bp2-site diff-site-config
to check that all the hosts are in sync. -
Restart the bpocore app.
$ solman "solution_app_restart bpdr.io.blueplanet.orchestrate:17.02.1-25 bpocore"
-
Exit the bpocore container using exit.
-
Confirm that the values are applied.
The command line arguments are logged to the /bp2/log/bpocore.config.log file in the bpocore container. The example below shows the override values appended after the defaults. The latter values take precedence.
2017-03-23 14:02:14,979 INFO com.cyaninc.bpocore.application.AppMain$Configuration Command line arguments: 2017-03-23 14:02:14,980 INFO com.cyaninc.bpocore.application.AppMain$Configuration JVM arguments: -Xmx1G -Xms1G -Xmx16G -Xms16G -Dcom.sun.management.jmxremote.port=7199 -Dcom.sun.management.jmxremote.rmi.port=7199 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Dlogback.configurationFile=logback.xml -Dcom.cyaninc.bpocore.application.init-config-file=deploy.conf
-
(Optional) To modify the JVM heap size, select System > System Health > Metrics to determine your JVM usage so you have a guideline for when the heap size needs to be increased.