[
https://issues.apache.org/jira/browse/IGNITE-12831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067436#comment-17067436
]
Ilya Shishkov commented on IGNITE-12831:
----------------------------------------
[~antonovsergey93], [[email protected]], as I see, you are right, local
caches has cluster-wide behaviour, and created and destroyed on all nodes. But
from the point of ordinary Apache Ignite user, the above phrase very implicitly
tells us about behaviour of create and destroy procedures.
So, IMHO, we should add to documentation some warnings about add/destroy, and
about that fact, that local caches are deprecated and will be removed from
Apache Ignite 3.0 and are strictly 'not recommended' for use in production.
> Invoking destroy of local cache on one node destroys local caches with the
> same name on all other nodes
> -------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12831
> URL: https://issues.apache.org/jira/browse/IGNITE-12831
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.8, 2.7.6
> Reporter: Ilya Shishkov
> Priority: Major
> Attachments: MyLocalCacheDestroyReproducer.java
>
>
> If you create caches with cache mode CacheMode.LOCAL and same name, but on
> different nodes, then all those caches will be destroyed after invoking
> destroy of cache on one of the cluster nodes.
> Expected behaviour: local cache should be destroyed only on the node invoking
> destroy.
> Reproducer in attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
