Hello dsetrakyan, > Are you trying to disable all cache updates and deletes altogether?
Short answer: No. Long answer: Looking that the discussion thread, I share Andrey Komev's views<http://mail-archives.apache.org/mod_mbox/incubator-ignite-dev/201505.mbox/ajax/%3CSNT406-EAS30127A948719AAB12EFC7CACFD50%40phx.gbl%3E>. My last mail was in a way, to express my surprise at how wide the impact from one client call to 'cache.close()', especially in an production environment. In the end, although unexpected, this behaviour can be managed on my end. Thank you. N2N DISCLAIMER: This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or N2N CONNECT BERHAD immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of N2N CONNECT BERHAD shall be understood as neither given nor endorsed by N2N CONNECT BERHAD accepts any responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mail is excluded to the fullest permitted by law. From: dsetrakyan [via Apache Ignite Users] [mailto:[email protected]] Sent: Thursday, 21 May, 2015 5:47 AM To: Augustus Thoo Subject: Re: IgniteCache.close() deletion behavior This has been a tricky point, as there is also another javadoc for CacheManager.destroyCache() method which states that it is equivalent to calling Cache.clear() and then Cache.close(). In this context, method Cache.close() should destroy the cache. However, given the ambiguity in the spec, we should take the approach of least surprise and have close() method release all the resources without deleting the whole cache. Looks like Alexey has already filed a ticket for it which should not be hard to fix: https://issues.apache.org/jira/browse/IGNITE-929 augustus.thoo wrote 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. Well, even in the absence of the "close" method, you still have Cache.remove(...) and Cache.clear(...) methods. Are you trying to disable all cache updates and deletes altogether? D. ________________________________ If you reply to this email, your message will be added to the discussion below: http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-close-deletion-behavior-tp338p353.html To unsubscribe from IgniteCache.close() deletion behavior, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=338&code=YXVndXN0dXMudGhvb0BuMm5jb25uZWN0LmNvbXwzMzh8NDMwMjE1MTE0>. NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteCache-close-deletion-behavior-tp338p355.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
