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

WiredTiger allows timestamped data without a stable or global timestamp

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints, RTS
    • None
    • Storage Engines
    • 5
    • Storage - Ra 2020-07-13, Storage - Ra 2020-07-27, Storage - Ra 2020-08-10, Storage - Ra 2020-08-24, Storage - Ra 2020-09-07, Storage - Ra 2020-09-21

      Creating this ticket as a place for discussion about weird timestamp configurations. Currently within WiredTiger you can timestamp data without ever setting an oldest or stable timestamp, which should created weirdness with rollback to stable on startup / shutdown. However rollback to stable current doesn't do anything if the stable timestamp is unset. I don't think it makes sense to have timestamped data without a stable / oldest timestamp.

      Most of this is follow on discussion from WT-6277's PR. https://github.com/wiredtiger/wiredtiger/pull/5811

      Additionally WT-5720 was created some time ago to document that currently WiredTiger allows you to have an oldest timestamp but no stable timestamp.

            Assignee:
            Unassigned Unassigned
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: