On this page本页内容
MongoDB Atlas
Use this tutorial to install MongoDB 4.4 Enterprise Edition on SUSE Linux Enterprise Server (SLES) using the zypper 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.
MongoDB 4.4 Enterprise Edition supports the following 64-bit SUSE Linux Enterprise Server (SLES) releases on x86_64 architecture:
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 4.4 Enterprise Edition on SLES also supports the s390x architecture on select platforms.
See Supported Platforms for more information.
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 zypper package manager.
Add the repository so that you can install MongoDB. Use the command appropriate for your version of SUSE:
If you’d like to install MongoDB packages from a previous release series such as 4.0, you can specify the release series in the repository configuration. For example, to restrict your SUSE 12 system to the 4.0 release series, use the following command:
To install MongoDB 4.4, issue the following command:
To install a specific release of MongoDB, specify each component package individually and append the version number to the package name, as in the following example:
You can specify any available version of MongoDB. However zypper upgrades the packages when a newer version becomes available. To prevent unintended upgrades, pin the packages by running the following command:
Previous versions of MongoDB packages use a different repository location. Refer to the version of the documentation appropriate for your MongoDB version.
By default, MongoDB instance stores:
/var/lib/mongo/var/log/mongodbIf you installed via the package manager, these default directories are created during the installation.
If you installed manually by downloading the tarballs, you can create the directories using mkdir -p <directory> or sudo mkdir -p <directory> depending on the user that will run MongoDB. (See your linux man pages for information on mkdir and sudo.)
By default, MongoDB runs using the mongod user account. If you change the user that runs the MongoDB process, you must also modify the permission to the /var/lib/mongo and /var/log/mongodb directories to give this user access to these directories.
To specify a different log file directory and data file directory, edit the systemLog.path and storage.dbPath settings in the /etc/mongod.conf. Ensure that the user running MongoDB has access to these directories.
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.
Follow these steps to run MongoDB Enterprise Edition. 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
|