Hi, I have been using Ignite for a week. I observed that calling close() would remove the cache from all of the nodes. Its Javadoc states:
/"Completely deletes the cache with all its data from the system on all cluster nodes."/ Note: Sourced from "ignite-core-1.0.4-javadoc.jar" under GridGain External Repository. Referring to javax.cache.Cache javadoc <http://grepcode.com/file/repo1.maven.org/maven2/javax.cache/cache-api/1.0.0/javax/cache/Cache.java#Cache.close%28%29> returns this : /"Closing a Cache signals to the CacheManager that produced or owns the Cache that it should no longer be managed."/ In my tests, I have configured a cache in XML, supported by 2 server nodes. Calling cache.close() from a client node did removed the cache from the server nodes. The only way to restore the cache as configured is by restarting the affected server nodes. If this is true, this behavior has far-reaching impact in production environment. Is there a way for server or admin to ignore or block any deletion calls from client nodes? I would like a way to configure the cache to be sticky in the grid so long as the configuration stays in the XML. Thanks. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-close-deletion-behavior-tp338.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
