Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-735

Avoid using readConcern snapshot in sharded transaction tests

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      Drivers should sync the transactions and transactions-convenient-api tests to this commit to avoid readConcern snapshot failures on sharded clusters:

      Message: SPEC-1411 Avoid using readConcern snapshot in sharded txn tests (#632)
      Branch: master
      https://github.com/mongodb/specifications/commit/a1c969be9fd75e61baef82f1296790c80e726b0b

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. PHPLIB-483 Avoid using readConcern snapshot in sharded transaction tests

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

          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

          Activity

            People

              Unassigned Unassigned
              shane.harvey@mongodb.com Shane Harvey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: