[SERVER-36049] Enable snapshot readConcern on mongos without atClusterTime Created: 10/Jul/18  Updated: 29/Oct/23  Resolved: 13/Jul/18

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: ShardedTxn:RouterSupport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-07-16
Participants:
Linked BF Score: 18

 Description   

To enable running tests in the core transactions suite that use snapshot readConcern against unsharded collections on a single shard, mongos needs to allow snapshot readConcern for more commands than it currently does. These commands do not need atClusterTime, since snapshot readConcern will currently only be used against a single shard and will not need to establish a global timestamp.

The commands are:

  • aggregate
  • distinct
  • find
  • findAndModify
  • insert
  • update
  • delete


 Comments   
Comment by Githook User [ 13/Jul/18 ]

Author:

{'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-36049 Enable snapshot readConcern w/o atClusterTime for txn commands on mongos
Branch: master
https://github.com/mongodb/mongo/commit/4e95b7ca81265d3a12eb7f9ae3952dc50238b6e8

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