This ensures that if a shard had cached a database entry without a version in a 4.0 cluster while in FCV 3.6, then upgrading the cluster to 4.2 binaries will cause the next request that has a database version attached to cause the shard to refresh and pick up the version and write it to its on-disk cache so that the version can also be picked up by secondaries.
- related to
-
SERVER-34458 Shards should always persist a database entry after refresh
- Closed