On this page本页内容
MongoDB Enterprise provides various features not available in the MongoDB Community edition, such as:
The following steps outline the procedure to upgrade a replica set from the MongoDB Community Edition to the MongoDB Enterprise Edition. For example, the steps can be used to upgrade MongoDB 4.0 Community to MongoDB 4.0 Enterprise.
Warning
Do not use these instructions to upgrade to another release version. To upgrade release versions, refer to the appropriate release upgrade instructions, such as Upgrade to MongoDB 4.2.
Depending on your operating system, you can install the MongoDB Enterprise binaries by using a package manager or by downloading the binaries manually.
If you have installed MongoDB Community using a package manager, follow the package manager instructions for your operating system:
During the installation, the package manager will remove the community packages; this will not affect the running deployment until you restart.
If you have not installed MongoDB using a package manager, you can manually download the MongoDB binaries from the MongoDB Download Center. Follow the manual instructions, including specific prerequisites for MongoDB Enterprise, for your operating system:
Important
Install to a location different from that of your current Community edition.
In the upgrade procedure, you will use the existing data directory and, if applicable, the existing configuration file.
Important
You cannot use the .msi
to install the Enterprise edition if you have the Community edition of the same release series installed on the same machine. That is, if you have version 4.4.0 Community edition installed, you cannot use the .msi
to install the 4.4.0 or 4.4.1 Enterprise edition.
Install the binaries:
To minimize downtime, you can upgrade from MongoDB Community to Enterprise Edition using a “rolling” upgrade by upgrading the members individually while the other members are available.
Upgrade the secondary members of the replica set one at a time:
mongod
instance.mongod
, specifying the same configuration options (e.g. same data directory, configuration file, etc.).Wait for the member to recover to SECONDARY
state before upgrading the next secondary member.
Once all the secondary members have been upgraded to Enterprise, connect a mongo
shell to the primary and use rs.stepDown()
to step down the primary and force an election of a new primary.
When rs.status()
shows that the primary has stepped down and another member has assumed PRIMARY
state, upgrade the stepped-down primary:
mongod
, specifying the same configuration options (e.g. same data directory, configuration file, etc.).Important
Before using any Enterprise features, ensure that all members have been upgraded to Enterprise edition.