[
https://issues.apache.org/jira/browse/IGNITE-12831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066904#comment-17066904
]
Sergey Antonov commented on IGNITE-12831:
-----------------------------------------
[~shishkovilja]
{quote}Expected behaviour: local cache should be destroyed only on the node
invoking destroy.{quote}
Your expectation is not valid. Look at the documentation [1]:
LOCAL mode is the most light weight mode of cache operation, as no data is
distributed to other cache nodes. It is ideal for scenarios where data is
either read-only, or can be periodically refreshed at some expiration
frequency. It also works very well with read-through behavior where data is
loaded from persistent storage on misses.* Other than distribution, local
caches still have all the features of a distributed cache, such as automatic
data eviction, expiration, disk swapping, data querying, and transactions.*
If you want to change that behavior please start a discussion on the dev list.
[1] https://apacheignite.readme.io/docs/cache-modes#local-mode
> 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)
