[SERVER-37523] Call supportsReadConcern for all commands in mongos Created: 09/Oct/18  Updated: 12/Dec/23

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: MaxH, ShardedTxn:RouterSupport, ShardingTechDebt, cs-subteam1, neweng, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-58176 Mongos does not validate readConcern ... Closed
Assigned Teams:
Cluster Scalability
Participants:

 Description   

Currently mongos only checks supportsReadConcern() for a command when it is received with snapshot level read concern, otherwise deferring the check to mongod. As mongos starts to make more decisions based on read concern (e.g. global snapshot timestamp selection) and for consistency of validation, we should consider always performing this check on mongos instead. This would require verifying / adding correct supportsReadConcern() definitions for each cluster command.



 Comments   
Comment by Max Hirschhorn [ 02/Nov/22 ]

SERVER-58176 may have only address this for the insert, update, and delete commands. It is worth double checking what additional work is needed to make the read concern validation consistent between mongos and mongod.

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