[SERVER-34049] Add a check for cluster commands which support readConcern majority on mongod Created: 21/Mar/18  Updated: 12/Apr/18  Resolved: 12/Apr/18

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-34050 Add a read concern "majority" passthr... Backlog
Sprint: Sharding 2018-04-09, Sharding 2018-04-23
Participants:

 Description   

SERVER-33061 added a call to reject command if it does not have snapshot read concern implementation. https://github.com/mongodb/mongo/blob/r3.7.3/src/mongo/s/commands/strategy.cpp#L225
However the supportsReadConcern on cluster commands for distinct, count, group need an overwrite to support readConcern majority to have the same behavior as before.
Eventually this check may become redundant as the cluster commands should support same readConcerns as mongod counterparts.



 Comments   
Comment by Misha Tyulenev [ 12/Apr/18 ]

The supportsReadConcern in mongos is called only after check if the readConcern level is snapshot. Hence there is no backwards incompatible change.

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