Metaspace OOM before reaching MaxMetaspaceSize

[Thomas Schatzl]

Hi,

On Mon, 2019-04-29 at 11:05 -0700, Shengpei Zhang wrote:
> Thanks David and Thomas :)
> 
> I checked our mmap limit, it is 64M. The # of mmap in the hs file is
> around 6K. I also did checked the current running process, it is
> about 8K. So I do not think it hit the mmap limit.
> 
> @Thomas
> Below is the rlimit output in the hs_err log, I am not sure how to
> interrupt it...
> 
> ---------------  S Y S T E M  ---------------
> 
> OS:CentOS Linux release 7.5.1804 (Core)
> uname:Linux 4.11.3-88_fbk23_4223_g7d3b7f39d8b1 #88 SMP Thu Jan 31
> 13:08:24 PST 2019 x86_64
> libc:glibc 2.17 NPTL 2.17
> rlimit: STACK 8192k, CORE infinity, NPROC 1030660, NOFILE 262144, AS
> infinity, DATA infinity, FSIZE infinity
> load average:99.10 107.68 103.71
> 
> One interesting article I saw is 
> https://bugs.openjdk.java.net/browse/JDK-8187709. Someone mentioned
> for (-XX:-UseCompressedOops) enabled machines, the native memory
> might be allocated at lower memory space, so the actual available
> memory is less than free memory. Could this be the cause?
> 

  as far as I know this only affects the default Solaris memory
manager, so not applicable.

Thanks,
  Thomas