Upgrade a Standalone to 5.0
On this page
Familiarize yourself with the content of this document, including thoroughly reviewing the prerequisites, prior to upgrading to MongoDB 5.0.
The following steps outline the procedure to upgrade a standalone
mongod from version 4.4 to 5.0.
If you need guidance on upgrading to 5.0, MongoDB professional services offer major version upgrade support to help ensure a smooth transition without interruption to your MongoDB application.
Upgrade Recommendations and Checklists
When upgrading, consider the following:
Upgrade Version Path
To upgrade an existing MongoDB deployment to 5.0, you must be running a 4.4-series release.
To upgrade from a version earlier than the 4.4-series, you must successively upgrade major releases until you have upgraded to 4.4-series. For example, if you are running a 4.2-series, you must upgrade first to 4.4 before you can upgrade to 5.0.
Check Driver Compatibility
Before you upgrade MongoDB, check that you're using a MongoDB 5.0-compatible driver. Consult the driver documentation for your specific driver to verify compatibility with MongoDB 5.0.
Upgraded deployments that run on incompatible drivers might encounter unexpected or undefined behavior.
Preparedness
Before beginning your upgrade, see the Compatibility Changes in MongoDB 5.0 document to ensure that your applications and deployments are compatible with MongoDB 5.0. Resolve the incompatibilities in your deployment before starting the upgrade.
Before upgrading MongoDB, always test your application in a staging environment before deploying the upgrade to your production environment.
Downgrade Consideration
Once upgraded to 5.0, if you need to downgrade, we recommend downgrading to the latest patch release of 4.4.
Prerequisites
Before you upgrade your standalone mongod, check
the 5.0 Performance Considerations for any
potential performance impacts when upgrading to 5.0.
Ensure TTL Config is Valid
Ensure that the TTL configuration is valid.
Before upgrading, remove or correct any TTL indexes that have
expireAfterSeconds set to NaN. In MongoDB 5.0 and later,
setting expireAfterSeconds to NaN has the same effect as
setting expireAfterSeconds to 0. For details, see
TTL expireAfterSeconds Behavior When Set to NaN.
Confirm Clean Shutdown
Prior to upgrading, confirm that your mongod instance was
cleanly shut down.
Feature Compatibility Version
The 4.4 instance must have featureCompatibilityVersion set
to "4.4". To check featureCompatibilityVersion:
db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
The operation should return a result that includes
"featureCompatibilityVersion" : { "version" : "4.4" }.
To set or update featureCompatibilityVersion, run the following
command:
db.adminCommand( { setFeatureCompatibilityVersion: "4.4" } )
For more information, see setFeatureCompatibilityVersion.
Consider Converting to Replica Set
Prior to upgrading, consider converting your standalone deployment to a replica set. Replica sets are the recommended deployment configuration for MongoDB.
Download 5.0 Binaries
Via Package Manager
If you installed MongoDB from the MongoDB apt, yum, dnf, or
zypper repositories, you should upgrade to 5.0 using your package
manager.
Follow the appropriate 5.0 installation instructions for your Linux system. This will involve adding a repository for the new release, then performing the actual upgrade process.
Manually
If you have not installed MongoDB using a package manager, you can manually download the MongoDB binaries from the MongoDB Download Center.
See 5.0 installation instructions for more information.
Upgrade Process
Warning
If you upgrade an existing instance of MongoDB to MongoDB
5.0.15, that instance may fail to start if fork: true is
set in the mongod.conf file.
The upgrade issue affects all MongoDB instances that use .deb or
.rpm installation packages. Installations that use the tarball
(.tgz) release or other package types are not affected. For more
information, see SERVER-74345.
To remove the fork: true setting, run these commands from a system
terminal:
systemctl stop mongod.service sed -i.bak '/fork: true/d' /etc/mongod.conf systemctl start mongod.service
The second systemctl command starts the upgraded instance after the
setting is removed.
Enable backwards-incompatible 5.0 features.
At this point, you can run the 5.0 binaries without the 5.0 features that are incompatible with 4.4.
To enable these 5.0 features, set the feature compatibility
version (fCV) to 5.0.
Tip
Enabling these backwards-incompatible features can complicate the downgrade process since you must remove any persisted backwards-incompatible features before you downgrade.
It is recommended that after upgrading, you allow your deployment to run without enabling these features for a burn-in period to ensure the likelihood of downgrade is minimal. When you are confident that the likelihood of downgrade is minimal, enable these features.
Run the setFeatureCompatibilityVersion command against the admin database:
db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } )
This command must perform writes to an internal system collection. If for any reason the command does not complete successfully, you can safely retry the command as the operation is idempotent.
Note
After the upgrade is complete, you may find a significant increase
in index sizes. To view index sizes, see dbStats.indexSize.
The index size increase is because of time window related data stored
in index keys.
If your indexes are significantly larger after upgrading and you would like to reduce the index sizes, contact your MongoDB technical support representative to discuss solutions.
Additional Upgrade Procedures
To upgrade a replica set, see Upgrade a Replica Set to 5.0.
To upgrade a sharded cluster, see Upgrade a Sharded Cluster to 5.0.