Description of problem:
If a cache instance with a 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 FileStore 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 FileStore should be pruned on cluster-join by default in this case
Steps to Reproduce:
1. Start a cache with filestore and >1 cluster nodes
2. add entires
3. stop one instance
4. remove/add/change entries
5. re-start the instance
The added/changed entries are correct after sync, but the removed entries are still available on the started instance
Removed entries are not available on any instance