How resilient is Eon when compute nodes are forcefully terminated (using the EC2 console) in an unclean fashion (without stopping the DB)? Can we still use revive_db with brand new compute nodes? If not, how do we get the DB back up?
Assuming that the communal storage was synced with the latest metadata. I'm trying to figure out what happens in a catastrophic failure of compute nodes.