Identified one corner case in testing that when the region server hosting both primary replica and the meta region is down, the client tries to reload the primary replica location from meta table, it is supposed to clean up only the cached location for specific replicaId, but it clears caches for all replicas. Please see
Since it takes some time for regions to be reassigned (including meta region), the following may throw exception
This exception needs to be caught and it needs to get cached location (in this case, the primary replica's location is not available). If there are cached locations for other replicas, it can still go ahead to get stale values from secondary replicas.
With meta replica, it still helps to not clean up the caches for all replicas as the info from primary meta replica is up-to-date.