If a cache instance with an unshared cache store is down and the cache is changed until the instance is back and join the cluster the cache can become inconsisstent.

If entries are deleted during downtime,

• the with stale object is loaded first if preload=true
• the local entries are updated with new and changed objects from the cluster
• removed entries from the cluster are not seen and therefore not deleted
  After complete sync (only) this instance will have stale objects.

From a consistence and performance perspective the store should be pruned on cluster-join by default in this case