Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-29494

WT validate should wait for explicit checkpoint

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • Fully Compatible
    • Repl 2017-12-18, Repl 2018-01-01, Repl 2018-01-15

      When running verifyTable on a WiredTiger file that is not clean, it forces a checkpoint. As we need to avoid creating a checkpoint with data that is not majority confirmed, this behavior is problematic.

      Instead, have full validate first take a MODE_S lock on the collection and then call a new method on the WiredTigerCheckpointThread that will trigger and wait for a new majority-confirmed checkpoint.

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            geert.bosch@mongodb.com Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: