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

Use clusterTime from oplog in 'change_streams_read_oplog_after_downgrade.js'

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • 15

      The current test code relies on the clusterTime returned by the insert command to be same as the time stamp written to the oplog. It looks like the clusterTime returned by the insert command is ahead of what is written in the oplog which is causing the test failure. Based on the oplog entires, it looks like there was a refresh on the collection.config.cache collection which incremented the clusterTime.

      To fix this, we should read the time stamp from the oplog, instead of relying on the output of the insert command.

            Assignee:
            arun.banala@mongodb.com Arun Banala
            Reporter:
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: