Describe the problem

Follower reads relies on having an up-to-date range descriptor. Currently our mechanisms to evict range descriptors are based primarily on key mismatches or failure to find the leaseholder. Unfortunately if our cached descriptor contains the leaseholder and we have an up-to-date leaseholder cache we'll never evict from our descriptor cache.

The code which handles the RangeNotFoundError here notes that the failure to find the replica could be due to the replica not yet having been initialized and that eviction could lead to thrashing.

The outcome is that sometimes follower reads will always hit a node which does not contain the range and then go on to hit the next closest follower.

To Reproduce

This needs reproduction steps.

Expected behavior

Follower reads should eventually occur.