Is it possible to see what, if any exception, is killing an Ignite Node in
the AFTER_NODE_STOP hook? I have an Ignite Cluster in Kubernetes and it's
difficult to recover from storage/wal related issues when my nodes restart
automatically. I'd like to do something like clear my index.bin file if the
node fails due to a CorruptedTreeException, or clear my storage directory
when the node fails because of a StorageException. Or would I have to find a
way to do this outside of Ignite?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to