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

WTKVEngine::setOldestFromStable must not choose a time earlier than the initialDataTimestamp

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.11
    • None
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2019-04-08, Storage NYC 2019-04-22

    Description

      The initialDataTimestamp is the earliest time the system knows the data to be consistent. setOldestTimestampFromStable will intentionally lag the oldest timestamp a few seconds behind the stable timestamp to provide a window for reads to get in.

      At startup, the initialDataTimestamp will be set to the checkpoint timestamp. The system has no history before this time. However, setOldestFromStable will communicate an earlier oldest_timestamp to WiredTiger. This means a transaction with a read_timestamp can come in that WT will allow, but does not have the history to correctly satisfy.

      Attachments

        Activity

          People

            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: