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

AllDurableTimestamp test does not enforce proper all_durable semantics

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2023-02-20

      In the AllDurableTimestamp unit test, we open a transaction at Timestamp(5, 1) but do not commit it yet. Then we fetch the all_durable timestamp and expect it to be Timestamp(5, 1). However, all_durable should not be Timestamp(5, 1) yet because the transaction has not committed.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: