I don't think anything except restarting the node can be done in this scenario. You can keep STOP segmentation policy and start node manually when VM is back, or try to use RESTART_JVM instead. Only note that RESTART_JVM works only for standalone nodes started with ignite.sh script.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Configuration-Recommendations-after-ESX-maintenance-failure-tp10878p10889.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
