Hi, Most likely the shutdown happened due to a segmentation policy.
By default the segmentation policy shut downs a node if it is kicked off the topology. Look for "Local node SEGMENTED:" message in the log of the failed node. As Val noted this can happen due to long GC pauses or network delays. The InterruptedException shouldn't have been printed out in this cases and it will be fixed soon https://issues.apache.org/jira/browse/IGNITE-2688 -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-node-stopped-tp3839p3846.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
