Hi Ignite team, We have a use case where a small portion of the dataset must answer successive queries that could be relatively expensive. For this, we create a temporary cache with that small subset of the dataset and operate on that new cache. At the end of the process, that cache is destroyed. The caches are created *partitioned* and *persistence* is enabled.The problem we are facing is the following. If during the reboot of a node, one of those "temporal" caches is destroyed (which is very likely since they have a short life), the node is unable to rejoin the cluster because it contains information about a cache that no longer exists. This is the exception:2020-06-02T02: 56: 22.326 + 00: 00 fa72f64b5d0f ignite: Caused by: class org.apache.ignite.spi.IgniteSpiException: Joining node has caches with data which are not presented on cluster, it could mean that they were already destroyed, to add the node to cluster - remove directories with the caches [cache-tempXXXXX, cache-tempYYYYY]Is this an expected behavior? Is it possible to skip this validation? Is there any way to indicate that it is a temporary cache?Thanks
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
