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

Allow mongos to retry on stale version and snapshot errors within a transaction

    XMLWordPrintableJSON

Details

    • Sharding NYC
    • Sharding 2019-03-25
    • 33

    Description

      Because of the problem described in SERVER-39624, mongos's ability to retry transaction statements that fail on stale version and snapshot errors without aborting the overall sharded transaction was disabled in favor of returning a TransientTransactionError label, so the client retries the entire transaction with a higher transaction number.

      This behavior could be problematic for long running transactions in particular because a stale version error on a late statement would force the entire transaction to be retried, instead of just the failed statement. The purpose of this ticket is to come up with a safe way to allow mongos to retry on these errors within a transaction that addresses the problem from SERVER-39624.

      Attachments

        Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-37207 Only retry failed writes in a batch on stale version errors in a transaction

          • Major - P3 - Major loss of function.
          • Backlog

          Task - A task that needs to be done. RUST-900 Remove extraneous calls to distinct in test runners

          • Unknown - Priority not determined yet.
          • Blocked

          Task - A task that needs to be done. CDRIVER-3301 Unskip txn tests with readConcern=snapshot against mongos

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-41532 Mongos can fail with "a non-retryable snapshot error" and "Unable to read from a snapshot due to pending collection catalog changes"

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. PYTHON-1901 Avoid using readConcern snapshot in sharded transaction tests

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39624 Reordering of transaction requests from mongos can lead shards to unexpectedly have in-progress transactions

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. CSHARP-2428 Support mongos pinning for sharded transactions

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. PHPLIB-677 Duplicate logic in unified test runner for avoiding StaleDbVersion errors with distinct

          • Trivial - P5 - Cosmetic problem like misspelt words or misaligned text.
          • Backlog

          Improvement - An improvement or enhancement to an existing feature or task. RUBY-1942 Avoid using readConcern snapshot in sharded transaction tests

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-47268 noop_createIndexes_not_blocked_by_txn.js fails on snapshot errors within a transaction

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-63887 SnapshotUnavailable error on sharded clusters/replica sets

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding-nyc Backlog - Sharding NYC
              jack.mulrow@mongodb.com Jack Mulrow
              Votes:
              3 Vote for this issue
              Watchers:
              33 Start watching this issue

              Dates

                Created:
                Updated: