Hi Ray, If your JVM process consumes more memory, then started swapping may cause JVM freeze, and as a consequence, throwing it out from the cluster. Check your free memory, disable swapping, if possible, or increase IgniteConfiguration.failureDetectionTimeout.
To check that guess you may use dstat and add -XX:+PrintGCApplicationStoppedTime property, it will log additional process stop times. Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/