• Manage Deployments >
• MongoDB Versions >
• Change the Version of MongoDB

Change the Version of MongoDB

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

Add a Custom MongoDB Build describes how to choose which versions of MongoDB are available to Cloud Manager.

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

Cloud Manager supports certain End of Life versions

MongoDB 3.6 reached its End of Life date on April 30, 2021. Cloud Manager doesn’t support Automation for MongoDB 2.6, 3.0, or 3.2. Cloud Manager still supports Automation using the MongoDB Agent for clusters running MongoDB 3.4 and 3.6.

Considerations

• Check the following documents for any considerations or compatibility issues before changing a deployment’s MongoDB version:
  • The MongoDB Release Notes
  • The documentation for your driver.
  • MongoDB Compatibility Matrix
• 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

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.

• 4.2 to 4.0
• 4.0 to 3.6
• 3.6 to 3.4

1

Unmanage, but continue to monitor, the deployment.

2

Downgrade the Feature Compatibility Version.

• Downgrade the 4.2 Standalone Feature Compatibility Version to 4.0
• Downgrade the 4.2 Replica Set Feature Compatibility Version to 4.0
• Downgrade the 4.2 Sharded Cluster Feature Compatibility Version to 4.0

Note

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

3

Import the deployment.

1. Import the deployment back into Cloud Manager.
2. Downgrade the MongoDB binaries with Ops Manager:
   • Downgrade the 4.2 Standalone MongoDB binaries to 4.0
   • Downgrade the 4.2 Replica Set MongoDB binaries to 4.0
   • Downgrade the 4.2 Sharded Cluster MongoDB binaries to 4.0

1

Unmanage, but continue to monitor, the deployment.

2

Downgrade the Feature Compatibility Version.

• Downgrade the 4.0 Standalone Feature Compatibility Version to 3.6
• Downgrade the 4.0 Replica Set Feature Compatibility Version to 3.6
• Downgrade the 4.0 Sharded Cluster Feature Compatibility Version to 3.6

Note

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

3

Import the deployment.

1. Import the deployment back into Cloud Manager.
2. Downgrade the MongoDB binaries with Ops Manager:
   • Downgrade the 4.0 Standalone MongoDB binaries to 3.6
   • Downgrade the 4.0 Replica Set MongoDB binaries to 3.6
   • Downgrade the 4.0 Sharded Cluster MongoDB binaries to 3.6

1

Unmanage, but continue to monitor, the deployment.

2

Downgrade the Feature Compatibility Version.

• Downgrade the 3.6 Standalone Feature Compatibility Version to 3.4
• Downgrade the 3.6 Replica Set Feature Compatibility Version to 3.4
• Downgrade the 3.6 Sharded Cluster Feature Compatibility Version to 3.4

Note

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

3

Import the deployment.

1. Import the deployment back into Cloud Manager.
2. Downgrade the MongoDB binaries with Ops Manager:
   • Downgrade the 3.6 Standalone MongoDB binaries to 3.4
   • Downgrade the 3.6 Replica Set MongoDB binaries to 3.4
   • Downgrade the 3.6 Sharded Cluster MongoDB binaries to 3.4

Procedure

1

Navigate to the Clusters view for your deployment.

1. If it is not already displayed, select the organization that contains your desired project from the office icon Organizations menu in the navigation bar.
2. If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
3. If it is not already displayed, click Deployment in the sidebar.
4. Click the Clusters 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.

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

(Optional) Update the featureCompatibilityVersion.

If you are upgrading to a new major version, and wish to enable features offered in the new major version, you must also update the featureCompatibilityVersion.

For each MongoDB deployment that you want to change:

1. Click the current featureCompatibilityVersion for the deployment.
2. Click the value that matches the desired version number.

6

Click Save.

7

Click Review & Deploy to review your changes.

8

Click Confirm & Deploy to deploy your changes.

Otherwise, click Cancel and you can make additional changes.

←   MongoDB Versions Add a Custom MongoDB Build  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.