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

Shards shouldn't abort local transaction on stale version error if router was stale

    XMLWordPrintableJSON

Details

    • Sharding

    Description

      As described in the design document for sharded transactions, shards don't need to abort their local transactions on stale version errors if the router was stale, because the shard won't have to refresh its metadata in this case and won't need to take a collection exclusive lock on the collection that triggered the exception.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: