[SERVER-22516] mongos should apply client's read preference to all commands Created: 08/Feb/16  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 1
Labels: AdiZ
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-22515 Implement Server Selection Spec's cha... Closed
is related to SERVER-29407 BadValue error when passing readPrefe... Closed
Assigned Teams:
Cluster Scalability
Backwards Compatibility: Major Change
Participants:

 Description   

If mongos is committed to matching the drivers Server Selection Spec, it needs to be updated to match behavior we decided on for drivers last year. See this section of the Server Selection Spec:

https://github.com/mongodb/specifications/blob/master/source/server-selection/server-selection.rst#use-of-read-preferences-with-commands

mongos should obey the "$readPreference" document sent with any command, regardless of the command name. The "whitelist" from the old Read Preferences spec is superseded by the new, simpler Server Selection Spec behavior.


Generated at Thu Feb 08 04:00:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.