When installing a new topology, we invalidate the cache entries that are no longer mapped to the local node. We also iterate over the entries in the cache stores and delete the ones that are no longer local, but this should only happen if the cache store is not shared. We had similar issues in the past, but this seems to be related to the new cache store API introduced in 6.0. After a closer look, it turns out the entries that are no longer local are deleted using an InvalidateCommand, which does not write to the cache stores. So the only issue is that iterating over the entire cache store can take a lot of time (and memory, because of ISPN-3937).