-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
Repl 2026-08-17, Repl 2026-08-31, Repl 2026-09-14, Repl 2026-09-28
-
None
-
None
-
None
-
None
-
None
-
None
-
None
P1 of work needed to make internal/external classification work for prepared transactions. We need to add isServerInitiatedTransaction as an optional, internal generic command argument and as a field of OperationSessionInfoFromClient. We also need to add an FCV-gated featureFlagServerInitiatedTransactionClassification in sharding_feature_flags.idl.
This is plumbing for forwarding a transaction's internal/external classification from routers to shards, so that a participant can attribute its transaction lifecycle metrics as server-initiated rather than user-initiated.
The next ticket is SERVER-133484.
- action item for
-
SERVER-130727 Investigate if we should add internal vs. external classification to transactions
-
- Blocked
-
- related to
-
SERVER-135397 Attach isServerInitiatedTransaction to the first command sent to each participant
-
- Closed
-