-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
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
-
5
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.
- split from
-
-
- Closed
-