[SERVER-77123] Make the read concern for TransactionResources come from the Prerequisites Created: 15/May/23  Updated: 29/Oct/23  Resolved: 16/May/23

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-2144-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-77124 Move TransactionResources under shard... Closed
is depended on by SERVER-77213 Move the all transactions-related sta... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-29
Participants:

 Description   

Currently, the TransactionResources is initialised with a ReadConcernArgs, but on one hand it never uses and on the other, it always takes from the OperationContext as opposed to from the AcquisitionRequest.

This ticket is to remove the read concern from the constructor of the TransactionResources and to make it come from the first acquisition. Furthermore, given that all acquisitions in the same session must have the same read concern, every subsequent one must match the previous ones.



 Comments   
Comment by Githook User [ 16/May/23 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-77123 Make the readConcern for TransactionResources come from prerequisites
Branch: master
https://github.com/mongodb/mongo/commit/6d34f15ca68a6c3e7ec67e5c75cce4d6bbf51aee

Generated at Thu Feb 08 06:34:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.