-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Service Arch
-
200
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.
- related to
-
SERVER-91294 Make config queries use a primaryPreferred read preference in clusters with a config shard
- Closed