ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1024
    • 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.

            Assignee:
            Kyra Ramesh Krishna
            Reporter:
            Kyra Ramesh Krishna
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: