Handle txnRetryCounter entirely within TransactionRouter

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding 2022-02-21, Sharding 2022-03-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The txnRetryCounter field added for internal transactions is only necessary for retrying transparently within a client transaction (tracked by SERVER-60369), so there's no need for callers to pass one to TransactionRouter::beginOrContinueTxn() on mongos and retry counter handling can take place entirely within that class.

            Assignee:
            Sanika Phanse (Inactive)
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: