The runtime that sized itself for the wrong machine
A JVM in a container with a 512 MB limit keeps being killed. Inside the container it reports the host's 64 GB as available memory and sizes its heap accordingly.
What is the underlying issue?
A JVM in a container with a 512 MB limit keeps being killed. Inside the container it reports the host's 64 GB as available memory and sizes its heap accordingly.
What is the underlying issue?