Upgrade a Standalone to 3.4
On this page
Starting in MongoDB 3.4.21, MongoDB 3.4-series removes support for Ubuntu 16.04 PPCLE.
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 the
glibcpackage to at least
glibc 2.23-0ubuntu5before running MongoDB. Systems with older versions of the
glibcpackage will experience database server crashes and misbehavior due to random memory corruption, and are unsuitable for production deployments of MongoDB
Before you attempt any upgrade, please familiarize yourself with the content of this document.
If you need guidance on upgrading to 3.4, MongoDB offers major version upgrade services to help ensure a smooth transition without interruption to your MongoDB application.
When upgrading, consider the following:
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.
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.
Once upgraded to 3.4, you cannot downgrade to a 3.2.7 or earlier version. You can only downgrade to a 3.2.8 or later version.
The following steps outline the procedure to upgrade a standalone
mongod from version 3.2 to 3.4.
If you installed MongoDB from the MongoDB
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.
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.
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.
setFeatureCompatibilityVersion command against the
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.