Upgrade a Standalone to 3.4
On this page
Note
Starting in version 3.4.21, MongoDB 3.4-series removes support for Ubuntu 16.04 POWER/PPC64LE.
For earlier MongoDB Enterprise versions that support Ubuntu 16.04 POWER/PPC64LE:
Due to a lock elision bug present in older versions of the
glibcpackage on Ubuntu 16.04 for POWER, you must upgrade theglibcpackage to at leastglibc 2.23-0ubuntu5before running MongoDB. Systems with older versions of theglibcpackage will experience database server crashes and misbehavior due to random memory corruption, and are unsuitable for production deployments of MongoDB
Important
Before you attempt any upgrade, please familiarize yourself with the content of this document.
If you need guidance on upgrading to 3.4, 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 3.4, you must be running a 3.2-series release.
To upgrade from a version earlier than the 3.2-series, you must successively upgrade major releases until you have upgraded to 3.2-series. For example, if you are running a 3.0-series, you must 3.2 before you can upgrade to 3.4.
Check Driver Compatibility
Before you upgrade MongoDB, check that you're using a MongoDB 3.4-compatible driver. Consult the driver documentation for your specific driver to verify compatibility with MongoDB 3.4.
Upgraded deployments that run on incompatible drivers might encounter unexpected or undefined behavior.
Preparedness
Before beginning your upgrade, see the Compatibility Changes in MongoDB 3.4 document to ensure that your applications and deployments are compatible with MongoDB 3.4. 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
Starting in MongoDB 7.0, you cannot downgrade your deployment's binary version without assistance from support.
To learn more, see Downgrade 7.0 to 6.0.
The following steps outline the procedure to upgrade a standalone
mongod from version 3.2 to 3.4.
Download 3.4 Binaries
Via Package Manager
If you installed MongoDB from the MongoDB apt, yum, dnf, or
zypper repositories, you should upgrade to 3.4 using your package
manager.
Follow the appropriate 3.4 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 3.4 installation instructions for more information.
Upgrade Process
Enable backwards-incompatible 3.4 features.
At this point, you can run the 3.4 binaries without the 3.4 features that are incompatible with 3.2.
To enable these 3.4 features, set the feature compatibility version to 3.4.
Warning
Enabling these backwards-incompatible features can complicate the downgrade process. For details, see Remove 3.4 Incompatible Features.
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: "3.4" } )
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.
Additional Upgrade Procedures
To upgrade a replica set, see Upgrade a Replica Set to 3.4.
To upgrade a sharded cluster, see Upgrade a Sharded Cluster to 3.4.