Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-91400

Allow transaction sub-router to retry on stale errors

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability

      We typically allow a transaction participant shard to retry on stale errors (StaleConfig, StaleDbVersion, ShardCannotRefreshDueToLocksHeld) if the request started the transaction on the shard, but we disallow retrying at all if the participant shard acted as a sub-router. We can consider allowing a shard that acted as a sub-router to retry if it targeted 0 or 1 other participant shards.

            Assignee:
            Unassigned Unassigned
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: