Navigation
You were redirected from a different version of the documentation. Click here to go back.

Change the Version of MongoDB

On this page

You can upgrade or downgrade MongoDB versions within the same Feature Compatibility Version (FCV) in Cloud Manager sharded clusters, replica sets, and standalone MongoDB instances while maximizing the availability of your deployments.

You can add custom-built versions of MongoDB for Cloud Manager to download.

If Cloud Manager doesn’t manage your deployment, change the version of MongoDB manually. To learn more, see upgrade tutorials for each MongoDB release.

Cloud Manager support for End of Life MongoDB versions

Cloud Manager doesn’t support Backup, Monitoring, or Automation for versions earlier than MongoDB 3.6.

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 5.0 to any version before 4.4.0
  • From version 4.4 to any version before 4.2.6
  • From version 4.2 to any version 4.0.12 (for Windows) or 4.0.7 (for Linux)
  • From version 4.0 to any version before 3.6.23

Prerequisites

Remove Incompatible MongoDB Features when Downgrading

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

1
2

Read the Downgrade Considerations and take appropriate action for unsupported features.

3
4

Import the deployment.

  1. Import the deployment back into Cloud Manager.
  2. Edit the deployment in Cloud Manager and select the downgraded version under the Version column.
1
2
3

Import the deployment.

  1. Import the deployment back into Cloud Manager.
  2. Edit the deployment in Cloud Manager and select the downgraded version under the Version column.
1
2
3

Import the deployment.

  1. Import the deployment back into Cloud Manager.
  2. Edit the deployment in Cloud Manager and select the downgraded version under the Version column.
1
2
3

Import the deployment.

  1. Import the deployment back into Cloud Manager.
  2. Edit the deployment in Cloud Manager and select the downgraded version under the Version column.

Procedure

1
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, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.