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

Recovery does not run after database opened with recover=error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.11, 3.6.0-rc2, WT3.0.0
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2017-10-23
    • Backport Requested:
      v3.4

      Description

      In the new test I wrote for WT-3257, I discovered a bug that if I run with log=(recover=error) on an unclean directory (properly getting the error that recovery must be run) and then, on the same unclean database, I run log=(recover=on) it does not properly recover all the data. The error run the first time moves a checkpoint LSN forward and we skip the earlier data.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sue.loverso Sue LoVerso
                Reporter:
                sue.loverso Sue LoVerso
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: