-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Repl 2026-08-31, Repl 2026-09-14, Repl 2026-09-28
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Investigate transaction metrics when a shard acts as a subrouter and recruits additional participants. Verify whether the originating internal/external classification is propagated; currently, recruited participants may be misclassified as external.
Acceptance criteria:
- Add a subrouter jstest eg. covering $lookup/$graphLookup within a transaction
- If misclassification is confirmed, add regression-covered handling; otherwise, document the expected metric skew and rationale
- action item for
-
SERVER-130727 Investigate if we should add internal vs. external classification to transactions
-
- In Progress
-