Container [pid=<process_ID>,containerID=<container_ID>] is running beyond physical memory limits. Current usage: <RSS> GB of <physical_limit> physical memory used; <VIRT> of <virtual_limit>virtual memory used. Killing container.
Application Errors
This page lists possible errors between applications and the Azul Zulu Prime Builds of OpenJDK (Azul Zulu Prime JVM).
If you get an error or warning message while running a Java application with the Azul Zulu Prime JVM, inspect the message and complete the steps suggested as a solution.
| Error | Description | Solution |
|---|---|---|
The error message displays when using Apache Hadoop with the Azul Zulu Prime JVM in the non-ZST mode. + For information about Azul Platform Prime usage of physical memory, see Unexpected Resident Set Size Memory Metric Shown by top and ps for Azul Platform Prime Java Processes. |
Disable the Hadoop physical memory check by setting yarn.nodemanager.pmem-check-enabled to false in the Hadoop configuration file yarn-site.xml. |
|
Container [pid=<process_ID>,containerID=<container_ID>] is running beyond virtual memory limits. Current usage: <RSS> of <physical_limit> GB physical memory used; <VIRT> of <virtual_limit> virtual memory used. Killing container. |
The error message displays when using Apache Hadoop with the Azul Zulu Prime JVM in both non-ZST and ZST modes. For information about Azul Platform Prime usage of physical and virtual memory, see the following:
|
Disable the Hadoop virtual memory check by setting yarn.nodemanager.vmem-check-enabled to false in the Hadoop configuration file yarn-site.xml. |
If you need additional assistance, contact [email protected].