[SERVER-65839] Add way to use transaction API without an initial opCtx Created: 20/Apr/22  Updated: 28/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Unresolved Votes: 0
Labels: txn-api-improvements
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from SERVER-61782 Make internal transaction run logic a... Closed
Assigned Teams:
Sharding NYC
Sprint: Sharding 2022-05-02, Sharding NYC 2022-05-16, Sharding 2022-06-27, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27
Participants:
Story Points: 5

 Description   

Currently the transaction API requires an operation context that it infers its execution context from, e.g. if the opCtx has a txnNumber but is not in a multi document transaction, then the API uses a retryable child session for its transaction with the opCtx's txnNumber in the session id.

If a caller has no operation context, e.g. the transaction comes from a primary only service, there should be a way to use the API that does not require an opCtx.



 Comments   
Comment by Jack Mulrow [ 26/May/22 ]

This ticket is nice to have, but doesn't need to block the completion of PM-2210, so I'm moving it out of the project and will treat it as a regular non-project ticket.

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