Hi Amit, No, Ignite node should not be stopped automatically because of a period of inactivity.
The one of possible reason for automatic shutdown may be a segmentation (node was segmented out of the cluster). Usually this happens because of long GC or temporary network problems, when node doesn't respond longer than 'failureDetectionTimeout'. So, I would suggest to enable additional logging info (-DIGNITE_QUIET=false JVM flag) and GC logs, this will help to understand the real cause of the issue. [1] https://apacheignite.readme.io/docs/cluster-config#failure-detection-timeout [2] https://ignite.apache.org/releases/2.1.0/javadoc/org/apache/ignite/plugin/segmentation/SegmentationPolicy.html Thanks. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-server-node-shutdown-tp16461p16477.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
