[SERVER-37630] Allow sharded transactions to run at majority read concern Created: 15/Oct/18  Updated: 29/Oct/23  Resolved: 01/Nov/18

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-11-05
Participants:

 Description   

Currently, sharded transactions only support snapshot level read concern. To enable majority read concern, this check should be relaxed, and the logic to select a global read timestamp should be disabled when the read concern level is not snapshot.



 Comments   
Comment by Githook User [ 01/Nov/18 ]

Author:

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

Message: SERVER-37630 Allow sharded transactions to run at majority read concern
Branch: master
https://github.com/mongodb/mongo/commit/337606645e0aba3d325f149bdfa1a64e59f9b8fc

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