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

Transactions that perform untimestamped reads do not check min visible snapshot for collection

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Repl 2019-04-22, Repl 2019-05-06, Repl 2019-05-20, Repl 2019-06-03

      Description

      After SERVER-38906, transactions with local or majority readConcern no longer read at a timestamp. This means that we will not check their read timestamp against the collection's minimum visible snapshot here, so we allow these transactions to read from collections that were created after the transaction was opened. This is illegal in the storage engine. Instead we should record what the most recent visible timestamp is before the transaction, and then use that to check the min visible time when reading a collection.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tess.avitabile Tess Avitabile
              Reporter:
              tess.avitabile Tess Avitabile
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: