Docs Menu

Docs HomeDevelop ApplicationsMongoDB Manual

Compatibility Changes in MongoDB 5.3

On this page

  • 2dsphere Document Index Keys
  • Change Streams and Orphan Documents
  • Intra-Cluster Authentication
  • Multiple Arbiters
  • Default db.stat() Settings
  • Downgrade Considerations

This page is a work in progress and will be updated with changes introduced in 5.3 that can affect compatibility with older versions of MongoDB.

To prevent out of memory errors, indexMaxNumGeneratedKeysPerDocument limits the maximum number of 2dsphere index keys generated for a single document.

See indexMaxNumGeneratedKeysPerDocument.

Starting in MongoDB 5.3, during chunk migration, change stream events are not generated for updates to orphaned documents.

Starting in MongoDB 5.3, SCRAM-SHA-1 cannot be used for intra-cluster authentication. Only SCRAM-SHA-256 is supported.

In previous MongoDB versions, SCRAM-SHA-1 and SCRAM-SHA-256 can both be used for intra-cluster authentication, even if SCRAM is not explicitly enabled.

Starting in MongoDB 5.3, support for multiple arbiters in a replica set is disabled by default. To enable support for multiple arbiters, start each node with the allowMultipleArbiters parameter.

Starting in MongoDB 5.3.0, 5.2.1, and 5.0.6, the dbStats command and the db.stats() method only report free space assigned to collections if the freeStorage parameter is set to 1.

The following sections provide information for removing backward-incompatible features from your deployment. If you are downgrading from MongoDB 5.3 to an earlier version, review the following sections to ensure that your deployment runs successfully after downgrading.

Starting in MongoDB 5.3, if you are using clustered collections, you must drop those collections before you can downgrade to an earlier MongoDB version.

You must drop time series collections before downgrading MongoDB 5.3 to MongoDB 5.0.5 or earlier.

See Time Series Collections.

←  Release Notes for MongoDB 5.3Release Notes for MongoDB 5.2 →