Thanks Mikhail. I suspected to increase the spark heartbeat/network timeout. But my question here is if an executor is lost, corresponding ignite node also gets out of cluster. In that case, ignite takes care of re balancing between the other active nodes right. My spark job was not killed and it keeps on running until I terminate the job, Instead my job is getting hung at the ignite cache load step for hours.
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
