Hi Denis, we see this exception too from a client when the cluster is restarted."IllegalStateException: Cache has been closed or destroyed: cache" we reconnect the client to the cluster by calling Ignition.stop and Ignition.start/ignite again and we are able to avoid this.
As far as cluster hanging goes, We are seeing many issues. optimistic txns hanging in commit(), if we try to kill nodes with hanging txns, the cluster hangs afterwards. unfortunately we cannot stop using Ignite at this point, we are already in production with some functionality. What can we send you to help us solve this issue? Thanks, Binti -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/One-failing-node-stalling-the-whole-cluster-tp5372p7199.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
