| Version | Change log |
| MongoDB 8.2.2 Nov 10, 2025 |
MongoDB 8.2 is a Minor Release, which means that it is supported for both MongoDB Atlas and on-premises deployments. MongoDB 8.2 introduces incremental improvements within a Major version release cycle. MongoDB 8.2 also includes changes introduced in MongoDB Rapid Release 8.1. This page describes changes introduced in the Rapid Release and MongoDB 8.2. Sharding: terminateSecondaryReadsOnOrphanCleanup Parameter MongoDB 8.2 adds the terminateSecondaryReadsOnOrphanCleanup parameter, which controls whether long-running read operations on secondary nodes automatically terminate before orphaned document deletion following a chunk migration. By default, this parameter is set to true. If a read operation on a secondary node begins before the chunk migration commits, MongoDB automatically terminates the operation before deleting the orphaned documents. In MongoDB versions before 8.2, these operations continue executing after orphaned document deletion and may silently miss documents without returning an error. To support this new behavior, the default value for orphanCleanupDelaySecs is now 3600 (previously 900). General Changes: Index Builds During Initial Sync: Starting in MongoDB 8.2, index builds during initial sync use 10% of available RAM by default. You can specify a different percentage of memory for MongoDB to use with the initialSyncIndexBuildMemoryPercentage parameter. By default, the amount of available memory must be between 200 MB and 16 GB, inclusive. You use the following parameters to specify different minimum and maximum thresholds for memory usage: initialSyncIndexBuildMemoryMinMB initialSyncIndexBuildMemoryMaxMB Query Statistics: Starting in MongoDB 8.2, the $queryStats output includes the following metrics on delinquent tickets: metrics.delinquentAcquisitions metrics.totalAcquisitionDelinquencyMillis metrics.maxAcquisitionDelinquencyMillis MongoDB considers an execution ticket as delinquent when acquisition takes too long. WiredTiger Cache Size Configura |
| MongoDB 8.2.1 Oct 3, 2025 |
MongoDB 8.2 is a Minor Release, which means that it is supported for both MongoDB Atlas and on-premises deployments. MongoDB 8.2 introduces incremental improvements within a Major version release cycle. MongoDB 8.2 also includes changes introduced in MongoDB Rapid Release 8.1. This page describes changes introduced in the Rapid Release and MongoDB 8.2. Sharding: terminateSecondaryReadsOnOrphanCleanup Parameter MongoDB 8.2 adds the terminateSecondaryReadsOnOrphanCleanup parameter, which controls whether long-running read operations on secondary nodes automatically terminate before orphaned document deletion following a chunk migration. By default, this parameter is set to true. If a read operation on a secondary node begins before the chunk migration commits, MongoDB automatically terminates the operation before deleting the orphaned documents. In MongoDB versions before 8.2, these operations continue executing after orphaned document deletion and may silently miss documents without returning an error. To support this new behavior, the default value for orphanCleanupDelaySecs is now 3600 (previously 900). General Changes: Index Builds During Initial Sync: Starting in MongoDB 8.2, index builds during initial sync use 10% of available RAM by default. You can specify a different percentage of memory for MongoDB to use with the initialSyncIndexBuildMemoryPercentage parameter. By default, the amount of available memory must be between 200 MB and 16 GB, inclusive. You use the following parameters to specify different minimum and maximum thresholds for memory usage: initialSyncIndexBuildMemoryMinMB initialSyncIndexBuildMemoryMaxMB Query Statistics: Starting in MongoDB 8.2, the $queryStats output includes the following metrics on delinquent tickets: metrics.delinquentAcquisitions metrics.totalAcquisitionDelinquencyMillis metrics.maxAcquisitionDelinquencyMillis MongoDB considers an execution ticket as delinquent when acquisition takes too long. WiredTiger Cache Size Configura |
| MongoDB 8.0.12 Jul 23, 2025 |
Internals bug fix: Incorrect BSONColumn handling of skip after non-zero RLE for double type |
| MongoDB 8.0.9 May 1, 2025 |
Internals bug fix: Incorrect BSONColumn handling of skip after non-zero RLE for double type |
| MongoDB 8.0.6 Mar 29, 2025 |
Sharding: SERVER-89138 Remove collection name limit of 235 for unsplittable collections SERVER-91121 Do not force a Shard Registry lookup if topology time doesn't change SERVER-95040 Add test coverage for checkMetadataConsistency interruptability SERVER-95544 setFeatureCompatibilityVersion, createCollection and moveCollection could cause a 3-way deadlock in config shards SERVER-99345 Prevent sharding/moving a time-series buckets collection without the 'timeseries' options on FCV 8.0+ Replication: SERVER-91180 dbCheck oplog entries contain duplicate field names in batchStart/batchEnd Query: SERVER-92640 $unionWith stage for explain does not use the router role API SERVER-95672 Indexes on array fields that contain subarrays does not include some results SERVER-97470 findAndModify: Mongos WriteConcernError Behavior Differs from Mongod SERVER-97629 Replace invariant with tassert when yielding SERVER-97860 Express path can return incorrect results when scanning a unique, multi-field index Catalog: SERVER-97220 [Test only] collection_catalog_two_phase_drops.js assumes write with journaling will advance the latest timestamp SERVER-97338 Prevent config.system.sessions from being created as sharded with its chunk on the config server SERVER-99290 Invalid timeseries buckets collections prevent completion of FCV 8.0 upgrade Storage: WiredTiger WT-10489 test_wt4803_history_store_abort hangs WT-12238 Investigate checkpoint cleanup for deleted pages WT-12846 Fix how compact walk handles EBUSY from checkpoint flush_lock WT-13186 Remove bounded cursor support when positioning truncate cursors WT-13447 Background compaction does not reset stats with run_once WT-13525 Migrate to AWS-based MacOS hosts WT-13546 Use internal session to create the history store table instead of default session WT-13592 Provide an option to control the number of RTS worker threads during startup/shutdown WT-13642 Create separate statistics for dirty leaf/internal pages WT-13713 Add WT stat to count create |
| MongoDB 8.0.5 Feb 22, 2025 |
Sharding: SERVER-89138 Remove collection name limit of 235 for unsplittable collections SERVER-91121 Do not force a Shard Registry lookup if topology time doesn't change SERVER-95040 Add test coverage for checkMetadataConsistency interruptability SERVER-95544 setFeatureCompatibilityVersion, createCollection and moveCollection could cause a 3-way deadlock in config shards SERVER-99345 Prevent sharding/moving a time-series buckets collection without the 'timeseries' options on FCV 8.0+ Replication: SERVER-91180 dbCheck oplog entries contain duplicate field names in batchStart/batchEnd Query: SERVER-92640 $unionWith stage for explain does not use the router role API SERVER-95672 Indexes on array fields that contain subarrays does not include some results SERVER-97470 findAndModify: Mongos WriteConcernError Behavior Differs from Mongod SERVER-97629 Replace invariant with tassert when yielding SERVER-97860 Express path can return incorrect results when scanning a unique, multi-field index Catalog: SERVER-97220 [Test only] collection_catalog_two_phase_drops.js assumes write with journaling will advance the latest timestamp SERVER-97338 Prevent config.system.sessions from being created as sharded with its chunk on the config server SERVER-99290 Invalid timeseries buckets collections prevent completion of FCV 8.0 upgrade Storage: WiredTiger WT-10489 test_wt4803_history_store_abort hangs WT-12238 Investigate checkpoint cleanup for deleted pages WT-12846 Fix how compact walk handles EBUSY from checkpoint flush_lock WT-13186 Remove bounded cursor support when positioning truncate cursors WT-13447 Background compaction does not reset stats with run_once WT-13525 Migrate to AWS-based MacOS hosts WT-13546 Use internal session to create the history store table instead of default session WT-13592 Provide an option to control the number of RTS worker threads during startup/shutdown WT-13642 Create separate statistics for dirty leaf/internal pages WT-13713 Add WT stat to count create |
| MongoDB 8.0.4 Dec 7, 2024 |
Logging: Starting in MongoDB 8.0, you can configure the Database Profiler to log slow operations based on the time that MongoDB spends working on that operation, rather than the total latency for the operation. This means that factors such as waiting for locks and flow control do not affect whether an operation exceeds the slow operation threshold. This change provides the following improvements for logging and query analysis: Slow queries are logged more accurately based on the time MongoDB spends processing the query. Query analysis tools such as the Query Profiler, Performance Advisor, and Search Query Telemetry report slow operations based on workingMillis instead of durationMillis. This change provides a more accurate view of problematic queries. Slow query logs include a metric for the time queued on execution tickets, queues.execution.totalTimeQueuedMicros. This metric helps identify whether an operation is slow because of the time it takes to complete, or the time it spends waiting to start. Database Profiler: When you specify a filter for the database profiler, you can log operations based on the new workingMillis metric. You can log operations based on both workingMillis and durationMillis and set each metric to a different threshold. Aggregation: BinData Conversion: Starting in MongoDB 8.0, you can use the $convert operator to perform the following conversions: String values to binData values binData values to string values MongoDB 8.0 also includes a new helper expression, $toUUID, which provides simplified syntax for converting strings to UUID values. $queryStats Change Stream Improvements: Starting in MongoDB 8.0, $queryStats improves tracking and reporting metrics for change streams. For more information, see $queryStats Change Streams Behavior. $rank and $denseRank Behavior: Starting in MongoDB 8.0, null and missing field values in $denseRank and $rank sortBy operations are treated the same when calculating rankings. This change makes the behavior of |
| MongoDB 8.0.0 Sep 23, 2024 |
Logging: Starting in MongoDB 8.0, you can configure the Database Profiler to log slow operations based on the time that MongoDB spends working on that operation, rather than the total latency for the operation. This means that factors such as waiting for locks and flow control do not affect whether an operation exceeds the slow operation threshold. This change provides the following improvements for logging and query analysis: Slow queries are logged more accurately based on the time MongoDB spends processing the query. Query analysis tools such as the Query Profiler, Performance Advisor, and Search Query Telemetry report slow operations based on workingMillis instead of durationMillis. This change provides a more accurate view of problematic queries. Slow query logs include a metric for the time queued on execution tickets, queues.execution.totalTimeQueuedMicros. This metric helps identify whether an operation is slow because of the time it takes to complete, or the time it spends waiting to start. Database Profiler: When you specify a filter for the database profiler, you can log operations based on the new workingMillis metric. You can log operations based on both workingMillis and durationMillis and set each metric to a different threshold. Aggregation: BinData Conversion: Starting in MongoDB 8.0, you can use the $convert operator to perform the following conversions: String values to binData values binData values to string values MongoDB 8.0 also includes a new helper expression, $toUUID, which provides simplified syntax for converting strings to UUID values. $queryStats Change Stream Improvements: Starting in MongoDB 8.0, $queryStats improves tracking and reporting metrics for change streams. For more information, see $queryStats Change Streams Behavior. $rank and $denseRank Behavior: Starting in MongoDB 8.0, null and missing field values in $denseRank and $rank sortBy operations are treated the same when calculating rankings. This change makes the behavior of |
