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

Visibility issues for readAfterClusterTime at level local

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • None
    • Storage Execution
    • ALL
    • Storage 2017-07-31

    Description

      When reading after a cluster time at level local, it is possible to have outstanding uncommitted transactions hide data assigned to an earlier cluster time. This is because optimes are not assigned by commit order.
      To fix this, we will need to block readAfterClusterTime reads until all transactions prior to the specified cluster time have committed.
      Note that it will be still be possible to return data before transactions after the specified cluster time have committed; this will be okay.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: