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

only snapshot, linearizable, and afterClusterTime reads should block on prepare conflicts

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.3
    • Replication
    • Fully Compatible
    • Repl 2018-08-27, Repl 2018-09-10

    Description

      Other read concern levels already accept that they can see partial transactions.

      Attachments

        Issue Links

          is depended on by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-36953 afterClusterTime reads should not block on prepare conflicts if their afterClusterTime is before the oldest prepare timestamp

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

          Task - A task that needs to be done. DOCS-12031 Docs for SERVER-36382: only snapshot, linearizable, and afterClusterTime reads should block on prepare conflicts

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-38499 Preparing transaction fails and triggers invariant if chosen timestamp is not greater than WiredTiger's latest active read timestamp

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

          Activity

            People

              samy.lanka@mongodb.com Samyukta Lanka
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: