org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node still alive?). Make sure that each GridComputeTask and GridCacheTransaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=6701f10e-8319-47ac-99b2-3521cfaf91ca, addrs=[HDD019/192.168.70.19:47100, /192.168.200.19:47100, /192.168.100.19:47100, /192.168.210.19:47100, /127.0.0.1:47100]]

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via nabble.com by Unknown author, 1 year ago
Failed to connect to node (is node still alive?). Make sure that each GridComputeTask and GridCacheTransaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=6701f10e-8319-47ac-99b2-3521cfaf91ca, addrs=[HDD019/192.168.70.19:47100, /192.168.200.19:47100, /192.168.100.19:47100, /192.168.210.19:47100, /127.0.0.1:47100]]
via Stack Overflow by rishi007bansod
, 1 year ago
Failed to connect to node (is node still alive?). Make sure that each ComputeTask and cache Transaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=797bf03b-3baf-4724-8eca-ccccec64605c, addrs=[01hw146471/192.168.140.52:47100, /10.0.42.1:47100, /0:0:0:0:0:0:0:1%lo:47100, /127.0.0.1:47100]]
via Google Groups by Anil, 10 months ago
Failed to connect to node (is node still alive?). Make sure that each ComputeTask and cache Transaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=7c3bd833-ee3c-44b3-978c-240fafedad56, addrs=[/172.16.41.3:47100, /0:0:0:0:0:0:0:1%lo:47100, /127.0.0.1:47100]]
via nabble.com by Unknown author, 7 months ago
Failed to connect to node (is node still alive?). Make sure that each ComputeTask and cache Transaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=58d0eb84-470d-495d-87dc-4b5088f5a96f, addrs=[10.17.32.45/10.17.32.45:47100, /0:0:0:0:0:0:0:1:47100, /127.0.0.1:47100]]
via Stack Overflow by Andreas Folkesson
, 1 year ago
Failed to connect to node (is node still alive?). Make sure that each ComputeTask and GridCacheTransaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=ad8937b4-eb38-442a-8e06-9625c6246d7b, addrs=[/xxx.xx.x.xxx:47100, /xxx.xx.x.xxx:47100]]
org.apache.ignite.IgniteCheckedException: Failed to connect to node (is node still alive?). Make sure that each GridComputeTask and GridCacheTransaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=6701f10e-8319-47ac-99b2-3521cfaf91ca, addrs=[HDD019/192.168.70.19:47100, /192.168.200.19:47100, /192.168.100.19:47100, /192.168.210.19:47100, /127.0.0.1:47100]]
at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2421)
at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2074)
at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1978)
at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$4500(TcpCommunicationSpi.java:234)
at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processRecovery(TcpCommunicationSpi.java:3122)
at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:2995)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.