> Is that acceptable to remove that then? It sounds like we want a check somehow to force it to load even during this period?

I guess it depends on the cache loader in use: if it's ClusterCacheLoader or a shared cache loader, forcing a load would be beneficial; if it's a local cache loader, it will contain either stale data or no data, depending on the `purgeOnStartup` setting. I guess forcing the load would still be the best choice.

OTOH, I'm not sure forcing the load if the local node is an owner in the write CH is ok in dist mode, I think it should happen only if the local node is an owner in the read CH.

> Also there are too many assumptions currently that prevent isPrimaryOwner from being used. If we do decide that [1] should be changed to be only primary owner then we should change this here as well (among so many other places).

If the command originated on a backup owner, it can read the entry from the local cache store. We only need to go to the primary owner if the originator is a non-owner (and if `L1.invalidationThreshold != 0`), so that the originator is registered as a requestor.