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

Turn off force on the recovery checkpoint

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Asparagus-StorEng - 2023-10-31

      Some time ago (I think January?) it was discovered that even though we set force=1 on the recovery checkpoint, this does not prevent it from skipping some trees and not checkpointing them. In particular, even with force the checkpoint only includes trees that are open; trees that are not open are skipped. This happens separately from the overt skip logic, so it isn't entirely obvious, and came as a bit of a surprise. And since we had been in some cases reasoning about things based on the assumption that the recovery checkpoint isn't skipped, it was a bit of an unpleasant surprise.

      Consequently it was decided that if it's going to be skipping trees anyway, we might as well turn off force on the recovery checkpoint, and furthermore if anything breaks as a result we want to know about it.

      Actually posting the change got postponed for various reasons and then temporarily forgotten, but now that releases have been branched it now seems like a reasonably good time.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            dholland+wt@sauclovia.org David Holland
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: