Re: Ignite Cache Expiry policy does not remove the cache from cache lists

[Denis Mekhanikov <dm...@gmail.com>]

There is no such mechanism.

Caches are rather static structured. They are not supposed to be created or
removed too often.
Cache creation and destruction are cluster-wide operations, that make all
operations stop until they are finished.

But if you really want to do it, you can schedule a task, that will iterate
over caches and destroy them if they are empty.

Denis

пн, 30 июл. 2018 г. в 20:31, okiesong <yj...@gmail.com>:

> Him first of all, thank you very much for your quick response!
>
> Just wondering, in that case, is there any scheduling job within Ignite
> that
> removes the cache itself after the records are removed due to expiry
> policy,
> so that when I call ignite.cacheNames() we know that it is removed? Thanks
> again!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>