The following messages are present in file: /storage/log/vcops/log/analytics-wrapper.log YYYY/MM/DD HH:MM:SS | INFO | jvm 1 | java.lang.OutOfMemoryError: Java heap space YYYY/MM/DD HH:MM:SS | INFO | jvm 1 | Dumping heap to /storage/db/vcops/heapdump/java_pid#####.hprof ...
Heap dump files have been recently created and can be found in the directory below: /storage/db/vcops/heapdump/
Environment
Aria Operations 8.18.3
Cause
High number of guest filesystem instanced metrics stored per object, ultimately resulting in the Java 'OutOfMemory' error.
Resolution
Run the following command on the Primary node:
su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"select * from metric_key order by metric_id \"" > /storage/db/metric_keys.txt
Get the total number of metric keys with the following command:
cat /storage/db/metric_keys.txt | wc -l
Get the total of Kubernetes related filesystem metric keys using the following command:
Compare the number of Kubernetes related filesystem keys with the total number of keys. If the number of Kubernetes related filesystem keys makes up the majority of the total keys, continue with the steps below to mitigate the issue:
Open the Aria Operations UI and browse to Operations >> Configurations >> Policy Definition
Select the Active policy (following change to be done on all Active policies)
Select these metrics one at a time and click on the blue Activated in the Instanced State column. In the pop out window, set the Collect toggle to off and click Save.(Instanced State now shows as "Deactivated")
Note: Upon turning off collection of the mentioned metrics as per the Resolution, it will not be able to see breakdown per Partition, the data will be represented by corresponding aggregated metrics.
If it is required to collect metrics for specific partitions, they can be specified as per the configuration screenshot below: