Navigation

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.

Note

Ops Manager automatically deploys config servers as replica sets for all new sharded cluster deployments using MongoDB 3.2 or later.

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.

Downgrading Limitations

You cannot downgrade a MongoDB deployment:

  • From version 3.6 to any version before 3.4.0
  • From version 3.4 to any version before 3.2.8

Prerequisites

Enable Desired MongoDB Versions

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

Remove Incompatible MongoDB Features when Downgrading

If the MongoDB deployment has set its Feature Compatibility Version to the same release series as its Version, you must first downgrade the featureCompatibilityVersion of the instance manually.

  1. Unmanage the deployment.

  2. Downgrade the deployment item manually.

    Note

    This removes any 4.0 incompatible features and sets the "featureCompatibilityVersion" : "3.6".

  3. Import the deployment back into Ops Manager.

  1. Unmanage the deployment.

  2. Downgrade the deployment item manually.

    Note

    This removes any 3.6 incompatible features and sets the "featureCompatibilityVersion" : "3.4".

  3. Import the deployment back into Ops Manager.

  1. Unmanage the deployment.

  2. Downgrade the deployment manually:

    Note

    This removes any 3.4 incompatible features and sets the "featureCompatibilityVersion" : "3.2".

  3. Import the deployment back into Ops Manager.

Procedure

1

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

2

On the line listing the deployment item, click Modify.

3

Verify the desired version number is in the version list.

In the Cluster Configuration section, the Cluster Settings heading lists the processes with their names, MongoDB versions, data directories and log files.

  1. Scroll to the Cluster Settings heading.
  2. Click the Version arrow for the first MongoDB process in the list.
  3. If the Version menu does not include the desired MongoDB version, enable the desired version in the Version Manager first, then return to this step.
4

Change the version of MongoDB for the deployment.

For each MongoDB process that you want to change:

  1. Click the current version number for the process.
  2. Click the desired version number.
5

Click Save.

6

Click Review & Deploy to review your changes.

7

Click Confirm & Deploy to deploy your changes.

Otherwise, click Cancel and you can make additional changes.