Ignite How eviction, expiry and rebalancing work with external CacheStore

Question

Ignite documentation explains clearly they automatically handles cache data rebalancing whern toplogy changes to keep the data evenly distributed within the cluster.

If I use CacheStore (https://apacheignite.readme.io/v1.9/docs/persistent-store) to persist cache entries with MySQL for example, will cache eviction/expiration happens even from my RDBMS ?

Example, I have a LRU eviction policy for cache size greater than 10. So will Ignite remove old entries even from my database also to keep most recent 10 entries ? For expiry, will it remove from database too ?

Answer 1

Neither of these mechanisms - eviction, expiry and rebalancing - have anything to do with CacheStore.

Eviction and expiry control how many entries are present in the Ignite cache based on the number and age of the entries. If an entry is expired/evicted it is not reflected in the backing DB.

Rebalancing changes where the cache data is physically located. It will not delete any data - not in the cache, not in the backing DB.