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

MongoDB Compatibility Matrix

This page describes compatibility between Ops Manager features and MongoDB.

MongoDB 2.4 reached its End of Life date in March 2016

  • Ops Manager will remove support for Automation and Backup of MongoDB 2.4 in Ops Manager 3.6 (estimated date: late 2017). Ops Manager groups must upgrade their MongoDB 2.4 deployments before the Ops Manager 3.6 release. Starting in Ops Manager 3.6, Automation will no longer support upgrades from MongoDB 2.4.
  • Ops Manager will continue to support Monitoring of MongoDB 2.4 deployments.

Compatible MongoDB Versions

The following table lists which MongoDB versions are compatible with each version of Ops Manager:

Ops Manager Compatible MongoDB versions
3.4 or later 2.4.3, 2.6, 3.0, 3.2, 3.4
2.0 or later 2.4.3, 2.6, 3.0, 3.2
1.6 or later 2.4.3, 2.6, 3.0

Note

To monitor a deployment running MongoDB 3.0 or later, you must use Monitoring Agent version 2.7.0 or later.

MongoDB Deployment Types

Using Ops Manager, you can configure all MongoDB deployment types: sharded clusters, replica sets, and standalones.

The shards in a sharded cluster must be replica sets. That is, a shard cannot be a standalone mongod. If you must run a shard as a single mongod (which provides no redundancy or failover), run the shard as a single-member replica set.

Note

You may not upgrade a sharded MongoDB deployment to version 3.4 if the deployment uses mirrored mongod instances as config servers. To allow the sharded deployment to be upgraded, see Convert Config Servers to a Replica Set. The conversion requires that the sharded deployment run MongoDB version 3.2.4 or later. Deployments running previous versions must upgrade to version 3.2.4 before an upgrade to version 3.4.