Hi, I guess you should remove -J-XX:+ExitOnOutOfMemoryError.
BR, Andrei 6/8/2021 3:42 PM, Naveen пишет:
HI We are using Ignite 2.8.1 we start Ignite node with below command and whenever node gets crashed with OOM it is not generating the heap dump in spite of having the below settings enabled. what could be the reason for this ? /usr/apache-ignite-2.8.1-bin/bin/ignite.sh -J-Xms2G -J-Xmx6G -J-XX:+AlwaysPreTouch -J-XX:+UseG1GC -J-XX:+ScavengeBeforeFullGC -J-XX:+DisableExplicitGC -J-XX:+HeapDumpOnOutOfMemoryError -J-XX:HeapDumpPath=/data1/ignite-log/heapdump -J-XX:+ExitOnOutOfMemoryError -J-XX:+PrintGC -J-XX:+PrintGCDetails -J-Xlog:gc*,gc+ref=debug,gc+heap=debug,gc+age=trace:file=/data1/ignite-log/gc-%p-%t.log:tags,time,level:filecount=10,filesize=20m -J-XX:+PrintFlagsFinal -J-XX:+UnlockDiagnosticVMOptions -J-Xlog:safepoint:file=/data1/ignite-log/safepoint.log -J-XX:+PrintSafepointStatistics -J-XX:PrintSafepointStatisticsCount=1 -J-Djava.net.preferIPv4Stack=true -J-DIGNITE_LONG_OPERATIONS_DUMP_TIMEOUT=600000 -J-DIGNITE_THREAD_DUMP_ON_EXCHANGE_TIMEOUT=true /usr/apache-ignite-2.8.1-bin/config/ignitedev-config.xml When allocated heap is exhausted, node is not getting killed, it just hangs and become unresponsive, this behavior of ignite node causing the issues. How do we kill the node when the whole heap memory is exhausted gracefully ? Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
