-
Type:
Question
-
Resolution: Cannot Reproduce
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.4.2
-
Component/s: MMAPv1
-
None
When starting up the mongod service on a standalone machine utilising a cloned drive from a stopped secondary, there is a start up delay of 2-3 minutes whilst stuff (unlogged) occurs.
Is there a way to prevent this delay ?
Process
1) Clone the data drive of a 3 machines secondary.
2) Load the drive to a standalone machine.
3) Start mongo service.
Log extract:
2017-03-04T10:13:05.132+0000 I CONTROL [initandlisten] MongoDB starting : pid=4420 port=37017 dbpath=c:/MongoDBDrive/data 64-bit host=mach-4
2017-03-04T10:13:05.132+0000 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] db version v3.4.2
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] git version: 3f76e40c105fc223b3e5aac3e20dcd026b83b38b
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] allocator: tcmalloc
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] modules: none
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] build environment:
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] distmod: 2008plus
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] distarch: x86_64
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] target_arch: x86_64
2017-03-04T10:13:05.133+0000 I CONTROL [initandlisten] options: { config: "c:\MongoDBBinaries\conf\mongo.conf", net: { http: { JSONPEnabled: false, RESTInterfaceEnabled: false, enabled: false }, port: 37017 }, operationProfiling: { mode: "off", slowOpThresholdMs: 2000 }, service: true, storage: { dbPath: "c:/MongoDBDrive/data", directoryPerDB: true, engine: "mmapv1" }, systemLog: { destination: "file", logAppend: false, path: "c:/MongoDBDrive/logs/logfile.log" } }
2017-03-04T10:13:05.201+0000 I JOURNAL [initandlisten] journal dir=c:/MongoDBDrive/data\journal
2017-03-04T10:13:05.201+0000 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed
2017-03-04T10:13:05.647+0000 I JOURNAL [durability] Durability thread started
2017-03-04T10:13:05.647+0000 I JOURNAL [journal writer] Journal writer thread started
2017-03-04T10:13:05.663+0000 I CONTROL [initandlisten]
2017-03-04T10:13:05.663+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
2017-03-04T10:13:05.663+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
2017-03-04T10:13:05.663+0000 I CONTROL [initandlisten]
*^^^^^^^^^VVVVVVV - nothing happening here in logs -----*
2017-03-04T10:16:28.776+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory 'c:/MongoDBDrive/data/diagnostic.data'
2017-03-04T10:16:28.933+0000 I STORAGE [initandlisten]
2017-03-04T10:16:28.933+0000 I STORAGE [initandlisten] ** WARNING: mongod started without --replSet yet 1 documents are present in local.system.replset
2017-03-04T10:16:28.933+0000 I STORAGE [initandlisten] ** Restart with --replSet unless you are doing maintenance and no other clients are connected.
2017-03-04T10:16:28.933+0000 I STORAGE [initandlisten] ** The TTL collection monitor will not start because of this.
2017-03-04T10:16:28.933+0000 I STORAGE [initandlisten] **
2017-03-04T10:16:28.934+0000 I STORAGE [initandlisten] For more info see http://dochub.mongodb.org/core/ttlcollections
2017-03-04T10:16:28.934+0000 I STORAGE [initandlisten]
2017-03-04T10:16:28.950+0000 I STORAGE [initandlisten] Service running
2017-03-04T10:16:28.963+0000 I NETWORK [thread1] waiting for connections on port 37017