Error
Error Code:
150
MongoDB Error 150: Outdated Cluster State
Description
The 'Stale Epoch' error indicates that a MongoDB replica set member or sharded cluster component is operating with an outdated understanding of the cluster's current state or configuration. This typically occurs when a node has missed critical updates regarding elections, primary changes, or configuration changes, leading to a discrepancy in its epoch view.
Error Message
Stale Epoch
Known Causes
4 known causesNetwork Connectivity Issues
A replica set member or config server temporarily lost network connectivity to the primary or other members, causing it to miss critical epoch updates.
Recent Replica Set Reconfig
The replica set configuration changed (e.g., primary changed, members added/removed) while the affected node was isolated or lagging, resulting in an outdated epoch.
Heavily Lagging Secondary
A secondary member is significantly behind the primary, missing critical oplog entries that include the latest epoch information.
Incorrect Startup Configuration
A node was started with incorrect or outdated configuration parameters, preventing it from correctly synchronizing with the current cluster epoch.
Solutions
Coming SoonDetailed step-by-step solutions for this error are being prepared. In the meantime, try these general troubleshooting tips:
General Troubleshooting Tips
- Check the error message carefully for specific details
- Review recent changes that might have caused the error
- Search for the exact error code in the official documentation
- Check log files for additional context
- Try restarting the application or service