In mongodb there is a base, it does not really need a collection of a hundred gigs. Mongodb has been updated and is now either re-indexing or restoring the base - all this is very long.

Delete this collection before starting the server

    1 answer 1

    1. Well, you can try to start and see db.currentOp () There will be a list of those operations that are running. Find in them the creation of an index, if any, or another operation that takes a long time to complete. And then try to kill this operation db.killOp (), then drop the collection if necessary.
    2. In theory, there is an option to run --noIndexBuildRetry which prohibits the launch of reindexing when the Monga starts https://docs.mongodb.com/v3.2/reference/program/mongod/#cmdoption-mongod-noindexbuildretry
    • just left for a day) and from the files the collection can not be thrown out? - eri