On this page本页内容
MongoDB Atlas
Use this tutorial to install MongoDB 4.4 Enterprise Edition on Red Hat Enterprise Linux, CentOS Linux, or Oracle Linux [1] using the yum
package manager.
MongoDB Enterprise Edition is available on select platforms and contains support for several features related to security and monitoring.
This tutorial installs MongoDB 4.4 Enterprise Edition. To install a different version of MongoDB Enterprise, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.
EOL Notice
MongoDB 4.4 Enterprise Edition supports the following 64-bit versions of Red Hat Enterprise Linux (RHEL), CentOS Linux, and Oracle Linux [1] on x86_64 architecture:
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 4.4 Enterprise Edition on RHEL / CentOS / Oracle also supports the PPC64LE and s390x architectures on select platforms.
See Supported Platforms for more information.
[1] | (1, 2) MongoDB only supports Oracle Linux running the Red Hat Compatible Kernel (RHCK). MongoDB does not support the Unbreakable Enterprise Kernel (UEK). |
Windows Subsystem for Linux (WSL) - Unsupported
MongoDB does not support the Windows Subsystem for Linux (WSL).
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Follow these steps to install MongoDB Enterprise Edition using the yum
package manager.
Create an /etc/yum.repos.d/mongodb-enterprise-4.4.repo
file so that you can install MongoDB enterprise directly using yum
:
Note
If you have a mongodb-enterprise.repo
file in this directory from a previous installation of MongoDB, you should remove it. Use the mongodb-enterprise-4.4.repo
file above to install MongoDB 4.4.
You can also download the .rpm
files directly from the MongoDB repository. Downloads are organized by Red Hat / CentOS version (e.g. 7
), then MongoDB release version (e.g. 4.4
), then architecture (e.g. x86_64
). Odd-numbered MongoDB release versions, such as 4.3
, are development versions and are unsuitable for production deployment.
Issue the following command:
To install a specific release, you must specify each component package individually along with the version number, as in the following example:
If you only install mongodb-enterprise=4.4.2
and do not include the component packages, the latest version of each MongoDB package will be installed regardless of what version you specified.
Although you can specify any available version of MongoDB Enterprise, yum
upgrades the packages when a newer version becomes available. To prevent unintended upgrades, pin the package by adding the following exclude
directive to your /etc/yum.conf
file:
Most Unix-like operating systems limit the system resources that a process may use. These limits may negatively impact MongoDB operation, and should be adjusted. See UNIX ulimit Settings for the recommended settings for your platform.
Note
Starting in MongoDB 4.4, a startup error is generated if the ulimit
value for number of open files is under 64000
.
By default, MongoDB runs using the mongod
user account and uses the following default directories:
/var/lib/mongo
(the data directory)/var/log/mongodb
(the log directory)mongod
.The default MongoDB directories are not created. To create the MongoDB data and log directories:
By default, MongoDB runs using the mongod
user account. Once created, set the owner and group of these directories to mongod
:
To use a data directory and/or log directory other than the default directories:
/etc/mongod.conf
and modify the following fields accordingly:
storage.dbPath
to specify a new data directory path (e.g. /some/data/directory
)systemLog.path
to specify a new log file path (e.g. /some/log/directory/mongod.log
)If you change the user that runs the MongoDB process, you must give the new user access to these directories.
Important
If SELinux is in enforcing
mode, you must customize your SELinux policy for MongoDB by making the following two policy adjustments:
cgroup
¶The current SELinux Policy does not allow the MongoDB process to access /sys/fs/cgroup
, which is required to determine the available memory on your system. If you intend to run SELinux in enforcing
mode, you will need to make the following adjustment to your SELinux policy:
checkpolicy
package installed:
mongodb_cgroup_memory.te
:
The MongoDB process is now able to access the correct files with SELinux set to enforcing
.
netstat
for FTDC¶The current SELinux Policy does not allow the MongoDB process to open and read /proc/net/netstat
, which is required for Full Time Diagnostic Data Capture (FTDC). If you intend to run SELinux in enforcing
mode, you will need to make the following adjustment to your SELinux policy:
checkpolicy
package installed:
mongodb_proc_net.te
:
Important
In addition to the above, you will also need to further customize your SELinux policy in the following two cases if SELinux is in enforcing
mode:
dbPath
, systemLog.path
, or pidFilePath
in RHEL 7.0 or later, and/ormongod
service to use the new directory:
where specify one of the following types as appropriate:
mongod_var_lib_t
for data directorymongod_log_t
for log file directorymongod_var_run_t
for pid file directoryNote
Be sure to include the .*
at the end of the directory.
where specify one of the following types as appropriate:
mongod_var_lib_t
for data directorymongod_log_t
for log directorymongod_var_run_t
for pid file directoryFor example:例如:
Tip
Be sure to include the .*
at the end of the directory for the semanage fcontext
operations.
/mongodb/data
:
/mongodb/log
(e.g. if the log file path is /mongodb/log/mongod.log
):
Follow these steps to run MongoDB Enterprise Edition on your system. These instructions assume that you are using the default settings.
Init System
To run and manage your mongod
process, you will be using your operating system’s built-in init system. Recent versions of Linux tend to use systemd (which uses the systemctl
command), while older versions of Linux tend to use System V init (which uses the service
command).
If you are unsure which init system your platform uses, run the following command:
Then select the appropriate tab below based on the result:
systemd
- select the systemd (systemctl) tab below.init
- select the System V Init (service) tab below.Start a mongo
shell on the same host machine as the mongod
. You can run the mongo
shell without any command-line options to connect to a mongod
that is running on your localhost with default port 27017:
For more information on connecting using the mongo
shell, such as to connect to a mongod
instance running on a different host and/or port, see The mongo Shell.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with MongoDB.
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:
Start a mongo
shell on the same host machine as the mongod
. You can run the mongo
shell without any command-line options to connect to a mongod
that is running on your localhost with default port 27017:
For more information on connecting using the mongo
shell, such as to connect to a mongod
instance running on a different host and/or port, see The mongo Shell.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with 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 any MongoDB packages that you had previously installed.
Remove MongoDB databases and log files.
By default, MongoDB launches with bindIp
set to 127.0.0.1
, which binds to the localhost network interface. This means that the mongod
can only accept connections from clients that are running on the same machine. Remote clients will not be able to connect to the mongod
, and the mongod
will not be able to initialize a replica set unless this value is set to a valid network interface.
This value can be configured either:
Warning
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.
For more information on configuring bindIp
, see IP Binding.
MongoDB Enterprise Edition is available from its own dedicated repository, and contains the following officially-supported packages:
Package Name | |||||||
---|---|---|---|---|---|---|---|
mongodb-enterprise |
A metapackage that automatically installs the component packages listed below. | ||||||
mongodb-enterprise-server |
Contains the mongod daemon and associated configuration and init scripts. | ||||||
mongodb-enterprise-mongos |
Contains the mongos daemon. | ||||||
mongodb-enterprise-shell |
Contains the mongo shell. | ||||||
mongodb-enterprise-cryptd |
Contains the mongocryptd binary | ||||||
mongodb-enterprise-tools |
A
|