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

Investigate if setting the oldest timestamp greater than the stable timestamp can be avoided

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • v7.3
    • Repl 2024-01-22, Repl 2024-02-05, Repl 2024-02-19, Repl 2024-03-04

      This ticket comes after the discussion in WT-12032 where it was found that the server sets the oldest ts after the stable ts by using the "force" field of the WT set_timestamp API. This is dangerous for the following reasons:

      • A checkpoint happens when the ts are out of order (for instance because of background compaction), see WT-12032.
      • Eviction happens when the ts are out of order which could result in data loss as update chains will pruned based on the oldest timestamp.

      Goals of this ticket:

      • Check if we can avoid setting the oldest timestamp greater than the stable timestamp in all cases.
      • Check if we can use "force" less liberally than we currently are.

            Assignee:
            xuerui.fa@mongodb.com Xuerui Fa
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            27 Start watching this issue

              Created:
              Updated:
              Resolved: