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

Setting a new stable timestamp in the past doesn't throw an error

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: APIs
    • None
    • Storage Engines
    • 1
    • Megabat - 2024-05-14

      Setting a new stable timestamp at an earlier point in the past (compared to the current stable timestamp) will be seemingly be "allowed" as this behaviour doesn't throw any errors, but internally nothing will be changed.

      This isn't strictly documented, and can be confusing. The scope of this ticket is to investigate into making this behaviour result in a failed assertion for illegal behaviour, as well as updating the documentation.

            Assignee:
            etienne.petrel@mongodb.com Etienne Petrel
            Reporter:
            clarisse.cheah@mongodb.com Clarisse Cheah
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: