0

I am trying to run mongodb --repair command after running for a considerable amount of time it shutsdown with following logs.

t.oplogTruncateAfterPoint" }
2019-07-11T20:36:14.034+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.036+0000 I STORAGE  [initandlisten] Repairing collection local.startup_log
2019-07-11T20:36:14.038+0000 I STORAGE  [initandlisten] Verify succeeded on uri table:collection-2--6589857005450806687. Not salvaging.
2019-07-11T20:36:14.044+0000 I INDEX    [initandlisten] build index on: local.startup_log properties: { v: 2, key: { _id: 1 }, name: "_id_", ns: "local.startup_log" }
2019-07-11T20:36:14.044+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.047+0000 I STORAGE  [initandlisten] Repairing collection local.system.replset
2019-07-11T20:36:14.048+0000 I STORAGE  [initandlisten] Verify succeeded on uri table:collection-7-2924198575954508702. Not salvaging.
2019-07-11T20:36:14.054+0000 I INDEX    [initandlisten] build index on: local.system.replset properties: { v: 2, key: { _id: 1 }, name: "_id_", ns: "local.system.replset" }
2019-07-11T20:36:14.054+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.056+0000 I STORAGE  [initandlisten] Repairing collection local.system.rollback.id
2019-07-11T20:36:14.058+0000 I STORAGE  [initandlisten] Verify succeeded on uri table:collection-4-2924198575954508702. Not salvaging.
2019-07-11T20:36:14.065+0000 I INDEX    [initandlisten] build index on: local.system.rollback.id properties: { v: 2, key: { _id: 1 }, name: "_id_", ns: "local.system.rollback.id" }
2019-07-11T20:36:14.065+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.072+0000 W ASIO     [initandlisten] No TransportLayer configured during NetworkInterface startup
2019-07-11T20:36:14.072+0000 I STORAGE  [initandlisten] finished checking dbs
2019-07-11T20:36:14.072+0000 I REPL     [initandlisten] shutting down replication subsystems
2019-07-11T20:36:14.072+0000 W REPL     [initandlisten] ReplicationCoordinatorImpl::shutdown() called before startup() finished.  Shutting down without cleaning up the replication system
2019-07-11T20:36:14.073+0000 I STORAGE  [WTOplogJournalThread] oplog journal thread loop shutting down
2019-07-11T20:36:14.073+0000 I STORAGE  [initandlisten] WiredTigerKVEngine shutting down
2019-07-11T20:36:14.073+0000 I STORAGE  [initandlisten] Shutting down session sweeper thread
2019-07-11T20:36:14.073+0000 I STORAGE  [initandlisten] Finished shutting down session sweeper thread
2019-07-11T20:36:14.502+0000 I STORAGE  [initandlisten] shutdown: removing fs lock...
2019-07-11T20:36:14.502+0000 I CONTROL  [initandlisten] now exiting
2019-07-11T20:36:14.502+0000 I CONTROL  [initandlisten] shutting down with code:0

Please Help.

  • What specific version of MongoDB server are you using and what is the role of this mongod (it looks like this may be part of a replica set)? What problem are you trying to resolve with repair? – Stennie Jul 14 at 23:29
  • It's mongodb 4.0.6... It is a part of the replicaset... I run docker to run Mongo instance... It was restarting all the time.. One of the recommendation I got was running Mongo with repair.. – pntripathi9417 Jul 14 at 23:46
  • 1
    I would recommend resyncing a replica set member rather than running repair (see the repairDatabase warning). Repair is equivalent to a salvage operation and may introduce inconsistencies if there are any data problems on a replica set member. The repairDatabase command has actually been removed in the upcoming MongoDB 4.2 release and command line mongod --repair is only for standalone. – Stennie Jul 15 at 0:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.