-
Enhancement
-
Resolution: Unresolved
-
P3
-
6.1.0
If running in a container, HotSpot currently doesn't take into account that all the machine memory in the machine might not be assigned to the container. See JDK-8170888
We should make a rule that somehow detects that the JVM was running in a container (IFF we can), and check if any flags are set to control the memory consumption, like -XX:+UseCGroupMemoryLimitForHeap, or if either -Xmx or -XX:MaxRAM has been set.
Notice that detecting that the JVM is in a container might be tricky.
- relates to
-
JMC-5563 Rules should optionally be able to take a standardized optimization target
- Open
-
JMC-5901 Utilize information from the host/container
- Open
-
JDK-8170888 [linux] Experimental support for cgroup memory limits in container (ie Docker) environments
- Resolved
-
JDK-8182070 Container Awareness
- Closed