Ensure write has occurred at or before the timestamp change stream started at in resharding change streams tests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Apr28-May09
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, we reserve at oplog slot at time "t", and then start the change stream from "t-1". In a unit test, there may be no writes at t-1, so the change stream would error with ChangeStreamHistoryLost. 

      We should fix this in all resharding unit tests that check the change streams monitor.

            Assignee:
            Kruti Shah
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: