Collection and database routers should not retry if shard is a txn participant

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • Hide

      You'll find a reproducible here.

      Show
      You'll find a reproducible here .
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      On SERVER-93430 collection and database routers stopped retrying if shard acted as a sub router. However, if the txn participant sends a request to itself through a collection/database router, the shard is not marked as a sub router and the operation is retried because txnRouter.isSafeToRetryStaleErrors returns true.

      We should prevent any txn participant from retrying a request executed under a collection/database router.

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

              Created:
              Updated: