RFR: 8284900: Check InitialHeapSize and container memory limits before startup [v8]
xpbob
duke at openjdk.java.net
Thu Apr 21 01:42:24 UTC 2022
On Wed, 20 Apr 2022 18:34:16 GMT, Ioi Lam <iklam at openjdk.org> wrote:
> Since you are testing `InitialHeapSize >= (julong) limit)`, the error message should be:
>
> > Initial heap size should be smaller than the container memory & swap limit
>
> The JVM will use memory outside of the heap (for example malloc, or code cache), so even if you set the `InitialHeapSize` to below the memory limit, the JVM might still get killed by OOM unpredictably.
>
> This PR catches obvious problems when `-Xms` is set way too large. However, I think we need to consider the larger issue of OOM killer when using Java in containers. I filed [JDK-8285277](https://bugs.openjdk.java.net/browse/JDK-8285277)
>
> I've started a discussion on [hotspot-dev](https://mail.openjdk.java.net/pipermail/hotspot-dev/2022-April/059463.html) about what approach we should use to handle container memory limits. Let's hold on with this PR until we have a consensus.
Thanks
The code I want to achieve here is similar to what happens when Java runs on a physical machine, with only Xms memory guaranteed
-------------
PR: https://git.openjdk.java.net/jdk/pull/8256
More information about the hotspot-gc-dev
mailing list