This articles describes the steps to take when a cluster is unable to discover its nodes. Steps in this articles assume Mongo is hosted as an add-on on Nex!™ PaaS but could in essence be applied to any Mongo hosting.
...
| Table of Contents | ||
|---|---|---|
|
...
| Code Block | ||
|---|---|---|
| ||
> rs.status()
{
"startupStatus" : 1,
"ok" : 0,
"errmsg" : "loading local.system.replset config (LOADINGCONFIG)"
} |
2 - Preferred steps
| Warning |
|---|
The steps described in this article are quite radical and must only be used in the event where the cluster cannot be reconfigured. |
We recommend first trying to reconfigure the Mongo cluster using the steps on this link.
...
First choose a container in your mongo addon - preferrably the last master if you can identify it
Code Block nex-cli cubes --addon name_of_mongo_addon
Stop all other mongo containers
Code Block nex-cli cubes:stop other_container_id
SSH to the rack hosting the container that is still alive
Code Block nex-cli racks:ssh 10.1.1.1
Connect to the container
Code Block sudo nex-attach my_container_id
Connect to Mongo using the Shell
Infocode mongo -u $MONGO_USER -p $MONGO_PASSWORD admin
Delete the local replication information. This command does NOT delete your actual data but will destroy uncommitted replication transactions.
Code Block use local db.dropDatabase()
- Exit the MongoShell and the container
On the rack issue a restart of the container. Upon restart the mongo instance will initiate a new replicaSet (previous one being deleted)
Code Block # Restart nex-restart --name my_container_id # Monitor logs docker logs -f my_container_id
Exit the rack and bring up the other nodes using the nex-cli
Code Block nex-cli cubes:start other_container_id