Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
SERVER ticket 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.
Change Description: Add a field "tooStale: true" at the top level of the replSetGetStatus reply from a secondary when it can't recover because it's fallen off the oplog. In other states, there is no tooStale field in replSetGetStatus.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
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
-
- Closed
-