Hello Pavel, Here's the log for for node ids = [429edc2b-eb14-414f-a978-9bfe35443c8c, 6783732c-9a13-466f-800a-ad4c8d9be3bf]. 6783732c-9a13-466f-800a-ad4c8d9be3bf.zip <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/6783732c-9a13-466f-800a-ad4c8d9be3bf.zip> 429edc2b-eb14-414f-a978-9bfe35443c8c.zip <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/429edc2b-eb14-414f-a978-9bfe35443c8c.zip> I examined the logs and looks like there's a network issue here because there's a lot of "java.net.NoRouteToHostException: No route to host" exception.
I did a little research and found this ticket may be the cause. https://issues.apache.org/jira/browse/IGNITE-8739 Will the client(spark executor in this case) retry data insert if I apply this patch when the network glitch is resolved? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
