Compatibility Changes in MongoDB 5.3
On this page
Important
MongoDB 6.3.1 is a rapid release and is only supported for MongoDB Atlas. MongoDB 6.3.1 is not supported for use on-premises. For more information, see MongoDB Versioning.
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.
2dsphere Document Index Keys
To prevent out of memory errors,
indexMaxNumGeneratedKeysPerDocument limits the maximum
number of 2dsphere index keys generated for a
single document.
Change Streams and Orphan Documents
Starting in MongoDB 5.3, during range migration, change stream events are not generated for updates to orphaned documents.
Intra-Cluster Authentication
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.
Multiple Arbiters
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.
Default db.stat() Settings
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.
Downgrade Considerations
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.
Clustered Collections
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.
Time Series Collections
You must drop time series collections before downgrading MongoDB 5.3 to MongoDB 5.0.5 or earlier.