-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
Repl 2026-09-28
-
None
-
None
-
None
-
None
-
None
-
None
-
None
P2 of work needed to make internal/external classification work for prepared transactions. We can add isServerInitiatedTransaction to TransactionRouter::SharedTransactionOptions and populate it based on the router's classification of the transaction. We can use attachTxnFieldsIfNeeded to append it as an internal generic argument on commands sent to participants, so that a shard can later attribute its transaction lifecycle metrics as server-initiated rather than user-initiated.
The argument should go on the wire only when it is true, only on the statement that begins the transaction on a given participant, and only when featureFlagServerInitiatedTransactionClassification is enabled.
The next ticket is SERVER-135398.
- action item for
-
SERVER-130727 Investigate if we should add internal vs. external classification to transactions
-
- Blocked
-
- is related to
-
SERVER-133484 Add the isServerInitiatedTransaction IDL definitions and feature flag
-
- Closed
-
-
SERVER-135398 Parse isServerInitiatedTransaction on shard participants and split prepared transaction metrics
-
- Closed
-