In a CSRS, and particularly in a config shard, it is common to experience lagged replica set nodes.

If the lagged node is the nearest to a request, a refresh can time out while waiting to satisfy the afterClusterTime.

The goal of this ticket is to make a proposal to exclusively use hedged reads when fetching metadata from CSRS for installing filtering or routing information, in order to be resilient to nearest lagged secondaries.