-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding EMEA 2023-05-29
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.
- depends on
-
SERVER-77124 Move TransactionResources under shard_role_api
- Closed
- is depended on by
-
SERVER-77213 Move the all transactions-related state from OperationContext to TransactionResources
- Blocked