-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Programmability
-
Programmability 2025-07-07
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Lifetime and cancelation issues also seem to be involved in many cases.
The output of this should be a document giving us a direction to pursue for future work.
- is related to
-
SERVER-81335 Query operations that avoid going through the network when a shard is targeting only itself should create a fresh operation context
-
- Open
-
-
SERVER-88539 Migration Destination Manager should not check out a session with a mixed opCtx and Client
-
- Backlog
-
-
SERVER-106855 Transaction id storage on opCtx interacts poorly with retryable writes.
-
- Backlog
-
-
SERVER-65839 Add way to use transaction API without an initial opCtx
-
- Open
-
-
SERVER-97686 Create API that enables releasing a session from an operation context's recovery unit
-
- Open
-
-
SERVER-100117 Make OpCtx inherit from Traceable
-
- Open
-
-
SERVER-85411 Evaluate the benefits of making `OpCtx` decorations role-specific
-
- Backlog
-
-
SERVER-86520 Create a opCtx on the router service during sharding initialization for mongod
-
- Backlog
-
-
SERVER-87866 Investigate if saveState/restoreState can release all storage engine resources
-
- Backlog
-
-
SERVER-92480 Unset txn state from opCtx when checking session in
-
- Backlog
-
-
SERVER-97772 Provide RSS-local OperationContext wrapper that only exposes interruptibility
-
- Backlog
-
-
SERVER-84514 Enforce implicit rules around use of OperationContext on a RemoteCommandRequest
-
- Backlog
-
-
SERVER-93667 Simplify opCtx
-
- Backlog
-