/storage/log/vcops/log/analytics-wrapper.log
2025/05/26 11:09:36 | INFO | jvm 1 | java.lang.OutOfMemoryError: Java heap space
2025/05/26 11:09:36 | INFO | jvm 1 | Dumping heap to /storage/db/vcops/heapdump/java_pid#####.hprof ...
/storage/db/vcops/heapdump/Aria Operations 8.18.3
High number of guest filesystem instanced metrics stored per object, ultimately resulting in the Java 'OutOfMemory' error.
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.txtcat /storage/db/metric_keys.txt | wc -lgrep "var/lib/kubelet/pods/" /storage/db/metric_keys.txt | wc -l
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:
Guest File System:/|Partition Utilization (%),
Guest File System:/|Partition Utilization (GB),
Guest File System:/|Partition Capacity (GB)
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: