Hi, It does look like nework issues. You might want to adjust network timeout to fit your use case: https://ignite.apache.org/docs/latest/clustering/network-configuration#connection-timeouts The main setting is IgniteConfiguration.failureDetectionTimeout
more useful details here: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html This might also be caused by GC issues. Check how much memory you've allocated to your process, collect GC logs and check what they say. https://ignite.apache.org/docs/latest/perf-and-troubleshooting/troubleshooting#detailed-gc-logs https://ignite.apache.org/docs/latest/perf-and-troubleshooting/memory-tuning Information on critial worker blocked message: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/handling-exceptions#failures-handling Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
