Docs Menu

Docs HomeDevelop ApplicationsMongoDB Manual

Release Notes for MongoDB 7.2

On this page

  • Patch Releases
  • General Changes
  • Resharding Improvements

Important

MongoDB 7.2 is a rapid release and is only supported for MongoDB Atlas. MongoDB 7.2 is not supported for use on-premises. For more information, see MongoDB Versioning.

Issues Fixed:

  • SERVER-84723 Sharded multi-document transactions can observe partial effects of concurrent DDL operations

  • All JIRA issues closed in 7.2.2

  • 7.2.2 Changelog

Issues fixed:

The rest of this page describes changes and new features introduced in MongoDB 7.2.

Starting in MongoDB 7.2, aggregation pipeline queries that attempt to use non-existent databases on mongos deployments return validation errors.

In previous versions, these aggregation queries return empty cursors.

Starting in MongoDB 7.2, the serverStatus command and the db.serverStatus() method outputs include the following new metrics:

Starting in MongoDB 7.2, you can specify any valid expression that resolves to a string for the field input of the $getField operator. In earlier versions, field accepts only string constants.

Starting in MongoDB 7.2, when you shard an empty collection with a hashed shard key, the operation creates one chunk per shard by default. Previously, the operation created two chunks by default.

MongoDB 7.2 introduces significant performance improvements in reshard collection operations, substantially reducing the amount of time the operation takes to run.

Additionally, if your application and cluster meet the necessary requirements and limitations, you can reshard the collection on the same key using the reshardCollection command to redistribute your collection, which is much faster than alternative range migration procedure.

The following options are added to the command:

Field
Description
forceRedistribution
Enables same-key resharding.

For examples, see Redistribute Data to New Shards.

← Release Notes