Mock replication coordinator may not update committed snapshot correctly

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2025-02-17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When using a mock replication coordinator, namely in unit tests, we always update the committed snapshot to this timestamp if it is higher. However, this is not necessarily correct as there may be an outstanding writes to the oplog before this one which have not yet committed. Thus, the committed snapshot may erroneously contain oplog holes until those outstanding writes commit.

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

              Created:
              Updated:
              Resolved: