From ArchWiki
Jump to: navigation, search

MongoDB (from humongous) is an open source document-oriented database system developed and supported by MongoDB Inc. (formerly 10gen). It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster.


Install mongodb from official repositories. You may also wish to still mongodb-tools, which provides tools such as mongoimport, mongoexport, mongodump, mongorestore, among others.

Start/Enable the mongodb.service daemon.

During the first startup of the mongodb service, it will pre-allocate space, by creating large files (for its journal and other data). This step may take a while, during which the database shell is unavailable.


To access the Database shell type in the terminal:

$ mongo


MongoDB won't start

Check that the systemctl service is configured to use the correct database location:

$ vi /usr/lib/systemd/system/mongodb.service

Add "--dbpath /var/lib/mongodb" to the "ExecStart" line:

ExecStart=/usr/bin/numactl --interleave=all mongod --quiet --config /etc/mongodb.conf --dbpath /var/lib/mongodb

Check that there is at least 3GB space available for its journal files, otherwise mongodb can fail to start (without issuing a message to the user):

$ df -h /var/lib/mongodb/

Check if the mongod.lock lock file is empty or not:

# ls  -lisa /var/lib/mongodb

If it is, stop mongodb.service. Run a repair on the database, specifying the dbpath (/var/lib/mongodb/ is the default --dbpath in Arch Linux):

# mongod --dbpath /var/lib/mongodb/ --repair

Upon completion, the dbpath should contain the repaired data files and an empty mongod.lock file.

Warning: In dire situations, you can remove the file, start the database using the possibly corrupt files, and attempt to recover data from the database. However, it is impossible to predict the state of the database in these situations. See upstream document for detail.

After running the repair as root, the files will be owned by the root user, whilst Arch Linux runs it under a different user. You will need to use chown to change the ownership of the files back to the correct user. See following link for further details: Further reference

# chown -R mongodb: /var/{log,lib}/mongodb/

Finally, if you copied the configuration file from mongodb documentation, remove these two lines and restart mongodb.service:

   fork: true

MongoDB complains about transparent_hugepage Kernel Setting

After starting the mongoDB, if you see some warnings about the transparent_hugepage you can permanently disable this System Setting by editing the following file (see FreeDesktop tmpfiles.d Manual):

w /sys/kernel/mm/transparent_hugepage/enabled - - - - never
w /sys/kernel/mm/transparent_hugepage/defrag - - - - never

If you want to disable only for this boot, you can use SysCtl or by simply echoing in the files like below:

# echo never > /sys/kernel/mm/transparent_hugepage/enabled
# echo never > /sys/kernel/mm/transparent_hugepage/defrag