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

ReplicationCoordinator waitUntilOpTimeForReadUntil should return NotYetInitialized when oplog has not been created.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.7.1
    • Replication
    • Replication
    • ALL
    • 16

    Description

      If a read with afterClusterTime read concern is received after a heartbeat has set the cluster time but before the oplog has been created, the system will crash trying to access the oplog. Instead, we should return NotYetInitialized to the user.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: