Hi, This might be due a network error or a GC pause. Use this guide to collect GC logs and look for long gc pauses: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/troubleshooting#detailed-gc-logs
[threadName=tcp-comm-worker, *blockedFor=110s]* ][tcp-comm-worker-#1%EDIFCustomerCC%][TcpCommunicationSpi] Connect timed out (consider increasing 'failureDetectionTimeout' configuration property) ][tcp-comm-worker-#1%EDIFCustomerCC%][TcpDiscoverySpi] Finished node ping [nodeId=1bd0d94b-0df0-42ab-a89a-e4320ccadbc3, res=false, time=16ms] Here the communication worker is blocked, meaning the network might be responsible. Check that all nodes are able to reach each other within timeout threshold limits. See : https://ignite.apache.org/docs/latest/clustering/network-configuration#connection-timeouts and: https://ignite.apache.org/docs/latest/clustering/network-configuration Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
