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

Set checkpoint LSN to existing log record. WT-1700

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      [~michaelcahill] Please review. Don't merge, but so we can talk. This changes the checkpoint LSN for WT-1700 from the next not-yet-allocated record, to the LSN of the last record. I was mistaken - this change does not fix all the issues in WT-1183 where we cannot run recovery on an incremental backup and then continue.

      In order to get that working we need to initialize the new write_start_lsn to the beginning of the last record in the log. Currently we do not walk the last file looking for that although it would be more correct. On initialization I set write_start_lsn to the same potential LSN when creating the new log file. So there is a window where that LSN is pointing to the not-yet-written checkpoint record.

      We could add code to do that walk, since it would only be done once at startup.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: