test/model should support crashpoints that result in recoverable checkpoints

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints, Test Model
    • None
    • Storage Engines, Storage Engines - Persistence
    • SE Persistence backlog
    • None

      Currently, test/model assumes that any checkpoint_crash_point will result in an incomplete non-recoverable checkpoint. However, this assumption does not hold when logging is enabled. From WT perspective, a crash that occurs after the checkpoint txn is committed (but before the metadata/turtle file is updated) will still result in a valid, recoverable checkpoint.

      To avoid test/model failures under this mismatch, I've temporarily prevented crash points from occurring after commit (specifically CKPT_CRASH_BEFORE_METADATA_SYNC) when logging is enabled. This is just a workaround and should be removed as part of this ticket.

      Definition of done:

      • test/model supports and correctly verifies crash scenarios that may result in recoverable checkpoints
      • Remove the workaround code before the log flush that is preventing us from reaching the post commit crash point when logging is enabled.
      • Ensure correct, deterministic behaviour under these crash scenarios with logging enabled and disabled
      • Add appropriate tests.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Mariam Mojid
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: