Hi, Make sure that -XX:+DisableExplicitGC is not used to avoid facing https://bugs.openjdk.java.net/browse/JDK-8142537.
Also use -XX:-HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=.. to take a heap dump and see where memory is being consumed. see: https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/clopts001.html Ignite uses a memory mapped file for WAL operations, which is the likely place where this direct byte buffer memory allocation is taking place. see: https://ignite.apache.org/docs/latest/persistence/native-persistence#wal-modes from doc: The memory-mapped file approach is used by default and can be switched off by setting the IGNITE_WAL_MMAP system property to false. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
