Hi, Are you doing cache.get from a client node? If so, is it possible that it was disconnected from topology and then reconnected back? There are scenarios when you can get this exception after this happens [1].
I would start with checking if there are any exceptions and/or warnings in the logs. [1] https://issues.apache.org/jira/browse/IGNITE-2766 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Cache-has-been-stopped-tp3389p3398.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
