See RFC discussion thread: https://mail.openjdk.org/pipermail/hotspot-runtime-dev/2022-December/059239.html

==================
When JDK-8281181 was backported to 17u and 11u, some users reported that their containerized workload experienced OOM.

Although the fix in JDK-8281181 is technically "correct" as CPU shares shouldn't be used to express a limit (see discussion in the CSR JDK-8281571), unfortunately some workload had been configured that way due to how the JDK historically mis-interpreted CPU shares.

Introducing a significant behavioral change in an update release probably isn't a good idea.

The proposal is to change the default value of UseContainerCpuShares from false to true, so users of update releases up to 17u will need to opt into the new behavior.


(PS, since UseContainerCpuShares has been removed in JDK 21, we may need to add it back as an obsolete flag to ease the transition from 17u to 21).