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

do not uassert if earliestOptime is unavailable for the optime serverStatus section

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Replication
    • Replication

    Description

      Currently, a node may not have an earliestOptime when in state STARTUP2 and doing an initial sync. The serverStatus command currently returns an error if you request the oplog server status section in this state. It would be better to simply not return the earliestOptime field, or to return a field that is effectively 0.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: