Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Change the Version of MongoDB

Overview

Ops Manager supports safe automatic MongoDB version upgrades and downgrades of managed MongoDB deployments while maximizing the availability of your deployment. Ops Manager can upgrade and downgrade sharded clusters, replica sets, and standalone MongoDB instances.

Configure Available MongoDB Versions describes how to choose which versions of MongoDB are available to Ops Manager.

If Ops Manager does not manage your deployment, you need to change the version of MongoDB manually. The MongoDB Manual provides upgrade tutorials with each release.

Considerations

  • Check the following documents for any considerations or compatibility issues before changing a deployment’s MongoDB version:

  • Plan the version change during a predefined maintenance window.

  • Change the MongoDB version on a staging environment before changing a production environment. Your staging environment should mirror your production environment. This can help avoid compatibility issues that may result in downtime for your production deployment.

  • Follow the MongoDB release notes when performing manual upgrades of replica sets and sharded clusters.

  • Perform any downgrades in two stages if your MongoDB configuration file includes options incompatible with the earlier MongoDB version:

    1. Remove the configuration settings specific to the newer MongoDB version. Deploy those changes.

      Example

      If you are running MongoDB version 3.0 with the engine option set to mmapv1, and want to downgrade to MongoDB 2.6, you must first remove the engine option. MongoDB 2.6 does not support that option.

    2. Update the MongoDB version. Deploy that change.

    Note

    • You may not downgrade a MongoDB deployment from version 3.4 to any version before 3.2.8.
    • Ops Manager blocks users attempts to downgrade from featureCompatibilityVersion=3.4 to featureCompatiblityVersion=3.2.

Procedure

1

Click Deployment, then the Processes tab, then the Topology view.

2

On the line listing the deployment item, click Modify.

3

In the Version field select the version. Then click Apply.

If the drop-down menu does not include the desired MongoDB version, you must first enable it in the Version Manager.

4

Click Review & Deploy to review your changes.

5

Review and approve your changes.

Ops Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. Otherwise, click Cancel and you can make additional changes.