Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.8.0-rc4
-
Fully Compatible
-
Linux
-
0
Description
Currently, mongod.lock is created in the data directory by the mmapv1 initialization code and is not present when another storage engine (eg. WiredTiger) is selected.
We should always ensure that this file is created (and locked) regardless of the storage engine used.
----------
The --shutdown switch (Linux-specific) doesn't work with WiredTiger because the --shutdown code checks for a non-existent mongod.lock file:
$ ./mongod --storageEngine=wiredTiger --fork --logpath=foo.log
|
about to fork child process, waiting until server is ready for connections.
|
forked process: 3680
|
child process started successfully, parent exiting
|
|
$ ./mongod --shutdown
|
There doesn't seem to be a server running with dbpath: /data/db
|
Version: b0014456dd
Attachments
Issue Links
- is duplicated by
-
SERVER-16781 Starting mongod with wiredtiger storage engine when dbpath is in use causes backtrace
-
- Closed
-
- related to
-
SERVER-17210 Crash can leave data inaccessible due to empty storage.bson file
-
- Closed
-