Investigate the implications of a shard retrying a failed command in a transaction

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      During SERVER-103699's work, we discovered that, in a transaction, a shard that acts as a router and routes the request to itself will retry upon StaleConifg.
      According to SERVER-93430, a shard should never retry a failed command if it's running inside a txn.

      We'll introduce a fix under SERVER-105486. However, we should understand the implications of retrying a failed command from a shard within a txn to discard the need for any CA.

            Assignee:
            Unassigned
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: