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

Add a 'tooStale' field to replSetGetStatus output when a node is in RECOVERING due to being too stale to sync from any available node

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.1
    • Replication
    • Minor Change
    • Repl 2019-07-15
    • 0

    Description

      When a mongod, which is part of a replica set, cannot recover because the oplog has rolled over, the mongod node stays in the RECOVERING state. There is no way to tell the difference between a node in RECOVERING that is actively applying oplog and will eventually transition to SECONDARY, and one that is in RECOVERING due to being too stale and will never recover unless a node becomes available that has an overlap with its oplog.

      Currently the only way to get this is through the logs, which keeps tools like ops/cloud manager from easily detecting and alerting when a node falls off the back of all available sync source oplogs.

      Attachments

        Issue Links

          Activity

            People

              jesse@mongodb.com A. Jesse Jiryu Davis
              shawn.mccarthy@mongodb.com Shawn McCarthy (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: