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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: