-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v8.0
-
CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-08-05
-
200
Using primaryPreferred as the read preference will ensure that operations read from the primary node, and in case it is unavailable, operations will read from secondary members.
The aim of this task is to ensure that all config queries use primaryPreferred as the read preference in clusters that use a config shard. Additionally, we need to guarantee that config queries switch to use nearest as the read preference when transitioning to a dedicated config server.
- is depended on by
-
SERVER-91526 Skip choosing the read preference when using the sharding catalog client in local mode
-
- Backlog
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-93033 Sharding cluster parameters cannot be accessed via MongoS
-
- Closed
-