Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6388

Fix-up out-of-order updates in the history store

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc11, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • 8
    • Storage - Ra 2020-06-15, Storage - Ra 2020-06-29

      Writing out of order timestamps to the history store causes visibility problems that are difficult to resolve. There are very few cases in MongoDB where they can use timestamps out of order. We should be able to keep the out of order content in cache until the section of the update chain that is out of order becomes globally visible and can be discarded.

      That's only going to be OK if the content isn't between the stable and oldest timestamps. i.e: checkpoint doesn't need to flush the content that has a range of out of order timestamps.

        1. Out of order timestamp management in WiredTiger.pdf
          48 kB

            Assignee:
            alex.cameron@mongodb.com Alex Cameron (Inactive)
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: