Hi, I've got a CacheStoreAdapter that implements write behind, and there's a case where the backend storage API can go away. And when this happens, I'd like to have Ignite _not_ continue to call the write behind methods, and instead, just stop. Otherwise, Ignite will completely hammer the non-existent backend and logging goes crazy. So is there a way to tell Ignite to stop calling the CacheStoreAdapter's write behind methods?
- Matt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
