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

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

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.7.1
    • Component/s: Replication
    • Replication
    • ALL
    • 16

      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.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: