OplogOrder test can read stale all_durable timestamp after rolling back oplog entries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.1, 5.0.15, 6.0.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.1, v6.0, v5.0, v4.4, v4.2
    • Execution Team 2022-11-14
    • 5
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The OplogOrder unit test rolls back two oplog entries and then checks that oplog visibility ruled are still honored. However, because the all_durable timestamp is not being updated to reflect this, the WiredTigerOplogManager can run and incorrectly move the oplog visibility timestamp forward again to its old value.

              Assignee:
              Gregory Noma
              Reporter:
              Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: