5.201
This topic provides information to tune your configuration to keep pace with Moab Workload Manager.
In this topic:
The number of threads Insight uses to process messages from Moab can be adjusted by changing the worker.count parameter in /opt/insight/etc/config.groovy.
If the Insight Server Host has many processors you may want to consider increasing the number of threads. For example, if the Insight host has 16 cores you may consider configuring 4 threads per core.
// 16 cores * 4 threads per core = 64 cores worker.count = 64
Once you have changed this value you will need to restart Insight for the changes to take effect.
5.201.2 Java Runtime Environment
Insightshould be run on Oracle® Java® Runtime Environment (JRE) version 8.
Normally Insight will fail to start and will log an error to /opt/insight/log/insight.log if run on an unsupported JRE. The following is a sample error message:
java.lang.Exception: Unsupported Java Virtual Machine (OpenJDK 64-Bit Server VM): see the Requirements section of the Insight Installation Guide.
This verification check prevents you from accidentally using a JRE which is known to have problems with Insight. However, there may be times when you want to force Insight to run on an unsupported JRE. This might happen if a supported JRE is not available for your platform. In these cases you tell Insight to skip the JRE verification check by setting the insight.skip.jre.verification parameter in the /opt/insight/etc/config.groovy configuration to "true". For example:
insight.skip.jre.verification = true
By default, Insight sets its JAVA_HOME environment variable to /user/java/latest. To use a different JRE, edit /opt/insight/etc/insight.conf and change the value of JAVA_HOME.
Related Topics