I have a Mongo
replica set with a few secondaries. A box, which hosts a secondary instance, crashed and lost the database.
I started the secondary Mongo
instance again and now it's stuck in STARTUP2 for more than 12 hours. Does it make sense ? The docs say Mongo
should be in STARTUP2 for a short period of time before entering the RECOVERING state
What does STARTUP2 exactly mean ? Is it copying the database from the primary ? How can I verify it (assuming the Mongo is running in Linux) ?
Best Answer
The answer of eoinbrazil is partly incorrect. A new Node can be in STARTUP2 for a long time. The link the posted says:
I'm administering a 700 GB collection and, when I add a new node the STARTUP2 state remains well over 24 hours. But you can still see if there is something happening, by watching if the database grows. You can see the size of the database on the new node with
or you can also observe the data directory, to see if it is still growing. (on linux with the commands ls, df, du, iotop, etc ....)