Error
Error Code:
149
MongoDB Error 149: No Config Primary
Description
This error indicates that the sharded cluster cannot find or elect a primary for its configuration server replica set. Without a primary config server, the sharded cluster cannot perform critical operations, leading to service disruption and potential data unavailability.
Error Message
No Config Primary
Known Causes
4 known causesConfig Server Replica Set Issues
The configuration server replica set failed to elect a primary due to insufficient healthy members, network partitions, or an inability to communicate within the set.
Network Connectivity Problems
Connectivity issues between the config servers themselves, or between config servers and other sharded cluster components, prevent proper replica set communication and primary election.
Data Corruption or Disk Issues
Corrupt data files or underlying disk problems on one or more config servers can prevent them from starting correctly or participating in a primary election.
Incorrect Configuration
Misconfiguration of the config server replica set, such as incorrect hostnames, ports, or replica set members, can prevent a primary from being successfully elected.
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