Release Notes for MongoDB 7.0 (Stable Release)
On this page
This page describes changes and new features introduced in MongoDB 7.0.
MongoDB 7.0 is a Major Release, which means that it is supported for both MongoDB Atlas and on-premises deployments. MongoDB 7.0 includes changes introduced in MongoDB Rapid Releases 6.1, 6.2, and 6.3. To see changes introduced in these rapid releases, see Changes Introduced in 6.X-Series Rapid Releases.
To learn more about the differences between Major and Rapid releases, see MongoDB Versioning.
Warning
Past Release Limitations
The Critical Advisories below affect some prior MongoDB versions. If your deployment depends on features impacted by a Critical Advisory, upgrade to the latest available patch release.
Issue | Affected Versions |
|---|---|
7.0.0 - 7.0.2 | |
7.0.0 - 7.0.2 (Time Series collections sharded by metaField embedded
objects) | |
7.0.0 - 7.0.5 | |
7.0.0 - 7.0.6 | |
7.0.0 - 7.0.6 |
Patch Releases
7.0.14 - Aug 26, 2024
Issues Fixed:
SERVER-82814 Support internal expr comparison operators when determining clustered collection scan bounds
SERVER-85892 $merge with pipeline after $documents returns error
SERVER-91195 Provide a generic backportable solution not to miss top-level timeseries collection options
SERVER-91625 Enable indexed plans for expressions with $$NOW, $$CLUSTER_TIME and $$USER_ROLES
WT-12643 Fix Eviction Server walk logic so that it's able to evict all pages
7.0.12 - Jun 28, 2024
Important
CSFLE and Queryable Encryption self-lookup may send malformed values in subpipelines
In MongoDB 7.0 prior to 7.0.12, a bug in query analysis of
certain complex self-referential $lookup subpipelines
may result in literal values in expressions for encrypted fields
being sent to the server malformed.
Should this occur, no documents are returned or written.
This issue affects the mongocryptd binary and mongo_crypt_v1
shared library in the following MongoDB Server versions:
7.3.0 - 7.3.3
7.0.0 - 7.0.11
6.0.0 - 6.0.16
5.0.0 - 5.0.28
Issues Fixed:
SERVER-64574 Upgrade MozJS/Spidermonkey to the latest ESR
SERVER-86674 Primary catch-up may believe it is caught up when it is not
SERVER-90485 $sort does not work as expected when used in conjunction with includeArrayIndex
SERVER-91362 Performance: Do not copy JS "scope" object if a cached JsExecution exists
WT-12736 Mark the page clean after re-instantiating the page with prepared updates
7.0.11 - May 23, 2024
Issues Fixed:
SERVER-85279 Don't run the FTDC collection stats collector on arbiters
SERVER-89495 Disable test parameters even when no setParameters are specified
SERVER-89625 Handle directoryPerDb and wiredTigerDirectoryForIndexes correctly when reporting namespaces and UUIDs during a backup
SERVER-90288 Bitwise query operators should interpret lowest addressable byte in BinData as least significant byte
WT-12609 Improve checkpoint cleanup and page eviction logic
7.0.9 - Apr 26, 2024
Issues fixed:
SERVER-79637 Incorrect query results in $lookup with TS foreign collection using a correlated predicate
SERVER-82349 Mongo 7 crashes on applyOps index delete/drops without a collection UUID
SERVER-86407 Validation does not produce complete results when it should
SERVER-88173 BinData bit comparisons give wrong results in many cases
WT-10807 Skip in-memory deleted pages as part of the tree walk
7.0.8 - Apr 3, 2024
Issues fixed:
SERVER-78556 Return default of internalInsertMaxBatchSize to 64
SERVER-79575 Fix numa node counting
SERVER-86583 Non-transactional snapshot read on unsharded collection may execute with mismatched sharding metadata
SERVER-87666 Query shape for $documents is unique on each execution
SERVER-88360 Remove "Sharding catalog and local catalog collection uuid do not match" tripwire assertion
7.0.7 - Mar 18, 2024
Issues fixed:
SERVER-84368 CreateIndex fails with StaleConfig if run from a stale mongos against a sharded non-empty collection
SERVER-84628 Startup warning in mongos for Read/Write Concern
SERVER-85459 [v7.0] bucketRoundingSeconds param is accepted by nodes on fCV 6.0, binary 7.0
SERVER-85869 Exhaustive find on config shard can return stale data
SERVER-87061 Sharded multi-document transactions can observe partial effects of concurrent reshard operation
7.0.6 - Feb 28, 2024
Important
Fix for MongoDB Server may allow successful untrusted connection
Due to CVE-2024-1351, in MongoDB 7.0 prior to 7.0.6, under certain
configurations of --tlsCAFile and
CAFile, MongoDB Server may skip peer certificate
validation which may result in untrusted connections to succeed.
This may effectively reduce the security guarantees provided by TLS and open connections that should have been closed due to failing certificate validation. This issue affects the following MongoDB Server versions:
7.0.0 - 7.0.5
6.0.0 - 6.0.13
5.0.0 - 5.0.24
4.4.0 - 4.4.28
CVSS Score: 8.8
CWE: CWE-295: Improper Certificate Validation
Issues fixed:
SERVER-72703 Downgrade $out's db lock to MODE_IX
SERVER-82353 Multi-document transactions can miss documents when movePrimary runs concurrently
SERVER-84338 Top level $or queries may lead to invalid SBE plan cache entry which returns wrong results
SERVER-84723 Sharded multi-document transactions can observe partial effects of concurrent DDL operations
WT-11062 Safe free the ref addr to allow concurrent access
7.0.5 - Jan 5, 2024
Issues fixed:
SERVER-33494 WT SizeStorer never deletes old entries
SERVER-80363 server default writeConcern is not honored when wtimeout is set
SERVER-83091 $or query can trigger an infinite loop during plan enumeration
SERVER-83830 On Enterprise build creating a collection in a replica set with the storageEngine.inMemory option breaks secondaries
WT-7929 Investigate a solution to avoid FTDC stalls during checkpoint
7.0.4 - Nov 27, 2023
Issues fixed:
SERVER-67962 Applying config.image_collection deletes needs better concurrency control
SERVER-69244 $merge fails when session default read concern has been set to "majority"
SERVER-79975 [Classic] Optimize large group keys
SERVER-81133 Speedup logic to persist routing table cache
SERVER-82446 $densify use case can result in documents outside of range
7.0.3 - Nov 9, 2023
Issues fixed:
SERVER-77506 Sharded multi-document transactions can mismatch data and ShardVersion
SERVER-79088 Improve SBE multi-planner performance for query which returns zero results
SERVER-81106 Recipient shard doesn't wait for the collection version to be locally persisted before starting the cloning phase
SERVER-81966 Avoid modification of previous ChunkMap instances during refresh
WT-11564 Fix RTS to read the newest transaction value only when it exists in the checkpoint
7.0.2 - Sep 29, 2023
Issues fixed:
SERVER-74954 Incorrect result when contained $or rewrites $elemMatch extra condition
SERVER-79771 Make Resharding Operation Resilient to NetworkInterfaceExceededTimeLimit
SERVER-79912 CheckReplDBHash reports failure with system.buckets collections due to invalid BSON
SERVER-79982 Batched catalog writers can run concurrently with HistoricalCatalogIdTracker::cleanup() and lead to incorrect PIT find results
SERVER-80488 Avoid traversing routing table in balancer split chunk policy
7.0.1 - Sep 5, 2023
Issues fixed:
SERVER-71627 Refreshing cached collection route info severely blocks all client requests for a cluster with 1 million chunks
SERVER-77183 $project followed by $group sometimes gives incorrect results
SERVER-80256 QueryPlannerAnalysis::explodeForSort should not assume that index scans produce disjoint results
7.0.0 - Aug 15, 2023
The rest of this page describes changes and new features introduced in MongoDB 7.0.
Atlas Search Index Management
Starting in MongoDB 7.0, you can manage Atlas Search indexes with mongosh
methods and database commands. Atlas Search index commands are only available
for deployments hosted on MongoDB Atlas, and require an
Atlas cluster tier of at least M10.
To manage Atlas Search indexes, use the following commands:
mongosh Methods
Name | Description |
|---|---|
Creates an Atlas Search index on a specified collection. | |
Deletes an existing Atlas Search index. | |
Returns information about existing Atlas Search indexes on a specified collection. | |
Updates an existing Atlas Search index. |
Database Commands
Name | Description |
|---|---|
Creates one or more Atlas Search indexes on a specified collection. | |
Deletes an existing Atlas Search index. | |
Updates an existing Atlas Search index. |
Aggregation Stages
Name | Description |
|---|---|
Lists sampled queries for all collections or a specific
collection. | |
Returns information about existing Atlas Search indexes on a specified collection. |
General Changes
OIDC Access Token Authentication Behavior
Starting in MongoDB 7.0, only one audience oidcIdentityProviders
field can be specified for OIDC access tokens. audience fields
with empty arrays or arrays of multiple strings are invalid.
For details, see oidcIdentityProviders Fields.
Drop a Hashed Shard Key Index
Starting in MongoDB 7.0.3 (and 6.0.12 and 5.0.22), you can drop the index for a hashed shard key.
This can speed up data insertion for collections sharded with a hashed
shard key. It can also speed up data ingestion when using
mongosync.
For details, see Drop a Hashed Shard Key Index.
Cache Refresh Time Fields
Starting in MongoDB 7.0, log messages for slow queries includes a new cache refresh time field.
Concurrent Storage Engine Transactions (Read and Write Tickets)
Starting in version 7.0, MongoDB uses a default algorithm to dynamically adjust the maximum number of concurrent storage engine transactions (including both read and write tickets) to optimize database throughput during overload.
The following table summarizes how to identify overload scenarios for MongoDB 7.0 and prior releases:
Version | Diagnosing Overload Scenarios |
|---|---|
7.0 | A large number of queued operations that persists for a prolonged period of time likely indicates an overload. A concurrent storage engine transaction (ticket) availibility of 0 for a prolonged period of time does not indicate an overload. |
6.0 and prior | A large number of queued operations that persists for a prolonged period of time likely indicates an overload. A concurrent storage engine transaction (ticket) availibility of 0 for a prolonged period of time likely indicates an overload. |
To learn more, see:
currentOp Metrics
Starting in MongoDB 7.0, the currentOp command and the
db.currentOp() method include these new fields:
$currentOp (aggregation) Metrics
Starting in MongoDB 7.0, the currentOp aggregation stage includes these new fields:
Compound Wildcard Indexes
Starting in MongoDB 7.0, you can create compound wildcard indexes. A compound wildcard index has one wildcard term and one or more additional index terms.
Use compound wildcard indexes to support queries on known patterns and to limit the total number of indexes in a collection.
Large Change Stream Events
Starting in MongoDB 7.0, if you have change stream events larger than 16 MB, you can use the new
$changeStreamSplitLargeEvent stage to split the events into
smaller fragments.
The following new metrics report information about large change stream events:
serverStatus Output Change
serverStatus includes the following new fields in its
output:
Slot-Based Query Execution Engine
Starting in MongoDB 7.0, the slot-based query execution engine improves performance for a wider range of find and aggregation queries.
Slow query log messages now
include a queryFramework field that indicates which query engine
completed the query:
queryFramework: "classic"indicates that the classic engine completed the query.queryFramework: "sbe"indicates that the slot-based query execution engine completed the query.
User Roles System Variable
Starting in MongoDB 7.0, you can use the new USER_ROLES
system variable to return the roles of the current user.
For use cases that include USER_ROLES, see the find, aggregation, view, updateOne, updateMany, and
findAndModify
examples.
New Sharding Statistics for Chunk Migrations
Available starting in MongoDB 7.1 (and 7.0, 6.3.2, 6.0.6, and 5.0.18).
MongoDB includes the following new sharding statistics for chunk migrations:
New Slow Query Log Message
Starting in MongoDB 7.0 (and 6.0.13, 5.0.24), the
totalOplogSlotDurationMicros in the slow query log message shows the
time between a write operation getting a commit timestamp to commit the
storage engine writes and actually committing. mongod supports
parallel writes. However, it commits write operations with commit
timestamps in any order.
To learn more, see Logging Slow Operations.
New Parameters
analyzeShardKey-related Parameters
MongoDB 7.0 adds the following parameters related to the
analyzeShardKey command:
autoMergerIntervalSecs Parameter
MongoDB 7.0 adds the autoMergerIntervalSecs parameter
which, when AutoMerger is enabled, specifies the amount of
time between automerging rounds, in seconds.
autoMergerIntervalSecs can only be set on config servers of sharded
clusters.
autoMergerThrottlingMS Parameter
MongoDB 7.0 adds the autoMergerThrottlingMS which, when
AutoMerger is enabled, specifies the minimum amount time
between merges initiated by the AutoMerger on the same
collection, in milliseconds. autoMergerThrottlingMS can only be set
on config servers of sharded clusters.
balancerMigrationsThrottlingMs Parameter
MongoDB 7.0 adds the balancerMigrationsThrottlingMs
parameter which allows you to throttle the balancing rate.
enableDetailedConnectionHealthMetricLogLines Parameter
MongoDB 7.0 adds the enableDetailedConnectionHealthMetricLogLines
parameter which lets you specify whether or not a set of log messages related to cluster connection health metrics appears in the
log.
oidcIdentityProviders Parameter
MongoDB 7.0 adds the oidcIdentityProviders parameter which allows
you to specify identity provider (IDP) configurations when using
OpenID Connect authentication.
configureQueryAnalysis-related Parameters
MongoDB 7.0 adds the following parameters related to the
configureQueryAnalysis command:
Security
Queryable Encryption General Availability
Starting in MongoDB 7.0, Queryable Encryption with equality queries is generally available (GA). Improvements in the GA make it incompatible with the Queryable Encryption Public Preview, which should not be used now that the feature is GA. For details, see Compatibility Changes in MongoDB 7.0.
KMIP 1.0 and 1.1 Support
MongoDB 7.0 (and 6.0.6) adds the useLegacyProtocol setting. This setting allows MongoDB
servers to connect to KMIP servers that use KMIP protocol version 1.0 or
1.1.
OpenSSL and FIPS Support
Starting in MongoDB 7.0 and 6.0.7, MongoDB supports OpenSSL 3.0 and the OpenSSL FIPS provider with these operating systems:
Red Hat Enterprise Linux 9
Amazon Linux 2023
Ubuntu Linux 22.04
For details, see TLS/SSL (Transport Encryption).
OpenID Connect
Starting in 7.0, MongoDB Enterprise provides support for OpenID Connect authentication. OpenID Connect is an authentication layer built on top of OAuth2. You can use OpenID Connect to configure single sign-on between your MongoDB database and a third-party identity provider.
Aggregation
New operators:
Name | Description |
|---|---|
Returns an approximation of the median, the 50th percentile, as a scalar value. This operator can be used as an accumulator and as an aggregation expression. | |
Returns an array of scalar values that correspond to specified percentile values. This operator can be used as an accumulator and as an aggregation expression. |
Month Name Specifier for $dateToString
MongoDB 7.0 adds the following format specifiers to use with the
$dateToString operator:
Specifiers | Description | Possible Values |
|---|---|---|
%b | Abbreviated month name (3 letters) | jan-dec |
%B | Full month name | january-december |
Time Series
MongoDB 7.0 removes most of the time series limitations from these operations that are based
on the delete command:
Sharding
Sharding Metadata Diagnostics
Starting in MongoDB 7.0, the checkMetadataConsistency command
is available to check sharding metadata at the cluster, database, and
collection levels for inconsistencies. These inconsistencies can originate
in cases such as:
Upgrades in cases where the cluster encountered a bug while running previous releases of MongoDB
Manual interventions that corrupt the cluster catalog
The following helper methods are now available through mongosh:
For more information on the inconsistencies the command checks for, see Inconsistency Types.
mergeAllChunksOnShard Command
Starting in MongoDB 7.0, the mergeAllChunksOnShard command
finds and merges all mergeable chunks that a shard
owns for a given collection.
The AutoMerger
Starting in MongoDB 7.0, the AutoMerger can automatically merge chunks that meet the mergeability requirements. The AutoMerger is enabled by default.
Starting in MongoDB 7.0, you can use the following methods to control the AutoMerger behavior:
enableAutoMerger Parameter for configureCollectionBalancing
Starting in MongoDB 7.0, the configureCollectionBalancing
command accepts the enableAutoMerger parameter. Use
enableAutoMerger to set whether or not the
AutoMerger takes this collection
into account.
rangeDeleterHighPriority Parameter for Deprioritizing Range deletions
Starting in MongoDB 7.0, you can prioritize or deprioritize cleanup of
orphaned documents over user operations
using the rangeDeleterHighPriority parameter.
operationsBlockedByRefresh Metrics Removed
MongoDB 7.0 removes the operationsBlockedByRefresh document that
contains statistics about operations blocked by catalog cache refresh
activity because the operationsBlockedByRefresh counters increased
on mongos for every operation that used collection routing
information even if the operation wasn't blocked by a catalog refresh
activity.
analyzeShardKey Command and db.collection.analyzeShardKey() Method
MongoDB 7.0 adds the analyzeShardKey command and the
db.collection.analyzeShardKey() method, which let you
calculate metrics for evaluating a shard key.
configureQueryAnalyzer Command and db.collection.configureQueryAnalyzer() Method
MongoDB 7.0 adds the configureQueryAnalyzer command, which
allows you to configure query sampling for a collection. MongoDB 7.0
also adds the db.collection.configureQueryAnalyzer(), which
wraps the configureQueryAnalyzer command. Sampled queries provide
information to analyzeShardKey to calculate metrics about read and
write distribution of a shard key.
Changes Introduced in 6.X-Series Rapid Releases
MongoDB 7.0 includes changes and features from the following Rapid Release versions:
Platform Support
Removed Platforms
MongoDB 7.0 removes support for RHEL 7 / CentOS 7 / Oracle 7 on the PPC64LE and s390x architectures.
Upgrade Procedures
Important
Feature Compatibility Version
To upgrade to MongoDB 7.0 from a 6.0 deployment, the 6.0 deployment
must have featureCompatibilityVersion set to 6.0. To check
the version:
db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
To upgrade to MongoDB 7.0, refer to the upgrade instructions specific to your MongoDB deployment:
If you need guidance on upgrading to 7.0, MongoDB professional services offer major version upgrade support to help ensure a smooth transition without interruption to your MongoDB application. To learn more, see MongoDB Consulting.
Downgrade Considerations
Only Single-Version Downgrades are Supported
MongoDB only supports single-version downgrades. You cannot downgrade to a release that is multiple versions behind your current release.
For example, you may downgrade a 7.0-series to a 6.0-series deployment. However, further downgrading that 6.0-series deployment to a 5.0-series deployment is not supported.
Downgrade Policy Changes
Starting in MongoDB 7.0:
Binary downgrades are no longer supported for MongoDB Community Edition.
You cannot downgrade your deployment's fCV to or from a rapid release version of MongoDB.
The
setFeatureCompatibilityVersioncommand requires an additional parameter,confirm, which must be set totrueto upgrade or downgrade fCV.If you upgrade or downgrade your deployment's fCV, you cannot downgrade your Enterprise deployment's binary version without assistance from support.
Backward-Incompatible Features
MongoDB 7.0 includes features that are not compatible with earlier releases. Downgrading from 7.0 to an earlier release requires that you remove data that uses these features.
For more information, see Backward-Incompatible Features.
Download
To download MongoDB 7.0, go to the MongoDB Download Center.
Report an Issue
To report an issue, see the MongoDB GitHub repository for instructions on how to file a JIRA ticket for the MongoDB server or one of the related projects.