-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
Repl 2026-09-28, Repl 2026-10-12
-
None
-
None
-
None
-
None
-
None
-
None
-
None
P3 of work needed to make internal/external classification work for prepared transactions.
We need to parse the new isServerInitiatedTransaction generic argument on a participant, and split prepared transaction counters by internal (server initiated) / external (user initiated) accordingly.
If the field isn’t set, we should fall back on the existing transport session check to classify transactions as internal or external. The field is passed into TransactionMetricsObserver::onStart() and used when incrementing total transaction stats.
The next ticket is SERVER-133855.
- action item for
-
SERVER-130727 Investigate if we should add internal vs. external classification to transactions
-
- Blocked
-
- is related to
-
SERVER-133855 Investigate/fix subrouter transaction classification
-
- Closed
-
- related to
-
SERVER-135397 Attach isServerInitiatedTransaction to the first command sent to each participant
-
- Closed
-