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

Ensure that we don't perform rollback to stable without a history store

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.0-rc7, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage - Ra 2020-05-18

      We introduced a bug as part of WT-5716 where we can potentially call rollback to stable without a history store. This results in a confusing ENOENT return propagated up from where we attempt to open the history store cursor.

      As part of this ticket, we need to ensure that we preserve the intent of that change since it is important. We must complete log recovery before checking whether the history store exists since it may result in entries added to the metadata file.

            Assignee:
            alex.cameron@mongodb.com Alex Cameron (Inactive)
            Reporter:
            alex.cameron@mongodb.com Alex Cameron (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: