Make full validate block until a new majority-confirmed checkpoint is created

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When doing verifyTable on a table with writes since the last checkpoint, WiredTiger will implicitly create a new checkpoint. However, with recovery to a timestamp no implicit checkpoints are allowed. So, the validate command needs to be changed to do the following:

      1. Lock the collection to validate in MODE_S
      2. Signal the checkpointing thread that a new checkpoint should be created
      3. Block until the new checkpoint is created

      This ensures that when we call verifyTable, no dirty data exists and no implicit checkpoint will be created.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: