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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.7.1
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
    • Operating System:
      ALL
    • Linked BF Score:
      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

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-repl Backlog - Replication Team
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: