- Install MongoDB >
- Install MongoDB Enterprise >
- Install MongoDB Enterprise on Red Hat Enterprise or CentOS
Install MongoDB Enterprise on Red Hat Enterprise or CentOS¶
On this page
Overview¶
Use this tutorial to install MongoDB Enterprise on Red Hat Enterprise Linux or CentOS
Linux versions 5, 6, and 7 from .rpm
packages.
Platform Support
This installation guide only supports 64-bit systems. See Platform Support for details.
Packages¶
MongoDB provides officially supported Enterprise packages in their own repository. This repository contains the following packages:
mongodb-enterprise
This package is a
metapackage
that will automatically install the four component packages listed below.mongodb-enterprise-server
This package contains the
mongod
daemon and associated configuration and init scripts.mongodb-enterprise-mongos
This package contains the
mongos
daemon.mongodb-enterprise-shell
This package contains the
mongo
shell.mongodb-enterprise-tools
This package contains the following MongoDB tools:
mongoimport
bsondump
,mongodump
,mongoexport
,mongofiles
,mongoimport
,mongooplog
,mongoperf
,mongorestore
,mongostat
, andmongotop
.
Init Scripts¶
The mongodb-enterprise
package includes various init scripts, including the init script /etc/rc.d/init.d/mongod
.
The package configures MongoDB using the /etc/mongod.conf
file in
conjunction with the init scripts. See
the Configuration File
reference for documentation of settings available in the configuration file.
As of version 3.0.15, there are no init scripts for
mongos
. The mongos
process is used only in
sharding. You can use the mongod
init script
to derive your own mongos
init script.
Considerations¶
Use the provided distribution packages as described in this page if possible. These packages will automatically install all of MongoDB’s dependencies, and are the recommended installation method.
The default /etc/mongod.conf
configuration file supplied by the
3.0 series packages has bind_ip
set to
127.0.0.1
by default. Modify this setting as needed for your
environment before initializing a replica set.
Changed in version 2.6: The package structure and names have changed as of version 2.6. For instructions on installation of an older release, please refer to the documentation for the appropriate version.
Install MongoDB Enterprise¶
When you install the packages for MongoDB Enterprise, you choose whether to install the current release or a previous one. This procedure describes how to do both.
Configure repository.¶
Create an /etc/yum.repos.d/mongodb-enterprise.repo
file so that
you can install MongoDB enterprise directly, using yum
.
For the latest 3.0 release of MongoDB Enterprise¶
Use the following repository file:
For a specific version of MongoDB Enterprise¶
To install
MongoDB Enterprise packages from a specific release
series, such as 2.4 or 2.6, you can
specify the release series in the repository configuration. For
example, to restrict your system to the 2.6 release series,
create a /etc/yum.repos.d/mongodb-enterprise-2.6.repo
file
to hold the following configuration information for the MongoDB
Enterprise 2.6 repository:
.repo
files for each release can also be found in the repository itself.
Remember that odd-numbered minor release versions (e.g. 2.5) are development versions and are unsuitable
for production deployment.
Install the MongoDB Enterprise packages and associated tools.¶
You can install either the latest 3.0 release of MongoDB Enterprise or a specific version of MongoDB Enterprise.
To install the latest 3.0 release of MongoDB Enterprise, issue the following command:
Optional: Manage Installed Version¶
Install a specific release of MongoDB Enterprise.¶
Specify each component package individually and append the
version number to the package name, as in the following example
that installs the 2.6.1
release of MongoDB:
Pin a specific version of MongoDB Enterprise.¶
Although you can specify any available version of MongoDB
Enterprise, yum
will upgrade the packages when a newer
version becomes available. To prevent unintended upgrades, pin
the package. To pin a package, add the following exclude
directive to your /etc/yum.conf
file:
Previous versions of MongoDB packages use different naming conventions. See the 2.4 version of documentation for more information.
When the install completes, you can run MongoDB.¶
Install MongoDB Enterprise From Tarball¶
While you should use the .rpm
packages as previously described, you may
also manually install MongoDB using the tarballs.
First you must install any dependencies as appropriate:
- Version 5
- Version 6
- Version 7
To perform the installation, see Install MongoDB Enterprise From Tarball.
Run MongoDB Enterprise¶
Prerequisites¶
Configure SELinux¶
Important
You must configure SELinux to allow MongoDB to start on Red Hat Linux-based systems (Red Hat Enterprise Linux or CentOS Linux).
To configure SELinux, administrators have three options:
Note
All three options require root
privileges. The first two options
each requires a system reboot and may have larger implications for
your deployment.
Disable SELinux entirely by changing the
SELINUX
setting todisabled
in/etc/selinux/config
.Set SELinux to
permissive
mode in/etc/selinux/config
by changing theSELINUX
setting topermissive
.Note
You can use
setenforce
to change to permissive mode; this method does not require a reboot but is not persistent.Enable access to the relevant ports (e.g. 27017) for SELinux if in
enforcing
mode. See Default MongoDB Port for more information on MongoDB’s default ports. For default settings, this can be accomplished by runningWarning
On RHEL 7.0, if you change the data path, the default SELinux policies will prevent
mongod
from having write access on the new data path if you do not change the security context.
You may alternatively choose not to install the SELinux packages when you are installing your Linux operating system, or choose to remove the relevant packages. This option is the most invasive and is not recommended.
Data Directories and Permissions¶
Warning
On RHEL 7.0, if you change the data path, the default SELinux
policies will prevent mongod
from having write access on
the new data path if you do not change the security context.
The MongoDB instance stores its data files in /var/lib/mongo
and its log files in /var/log/mongodb
by default,
and runs using the mongod
user account. You can specify alternate log and data file
directories in /etc/mongod.conf
. See systemLog.path
and storage.dbPath
for additional information.
If you change the user that runs the MongoDB process, you
must modify the access control rights to the /var/lib/mongo
and
/var/log/mongodb
directories to give this user access to these
directories.
Procedure¶
Verify that MongoDB has started successfully¶
You can verify that the mongod
process has started
successfully by checking the contents of the log file at
/var/log/mongodb/mongod.log
for a line reading
where <port>
is the port configured in /etc/mongod.conf
, 27017
by default.
You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
Begin using MongoDB.¶
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. See Getting Started for the available editions.
Before deploying MongoDB in a production environment, consider the Production Notes document.
Later, to stop MongoDB, press Control+C
in the terminal where the
mongod
instance is running.
Uninstall MongoDB¶
To completely remove MongoDB from a system, you must remove the MongoDB applications themselves, the configuration files, and any directories containing data and logs. The following section guides you through the necessary steps.
Warning
This process will completely remove MongoDB, its configuration, and all databases. This process is not reversible, so ensure that all of your configuration and data is backed up before proceeding.
Remove Packages.¶
Remove any MongoDB packages that you had previously installed.
Remove Data Directories.¶
Remove MongoDB databases and log files.