tencent cloud

TencentDB for MongoDB

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Strengths
Use Cases
Cluster Architecture
Product Specifications
Features
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
MongoDB Pricing
Billing Formula
Payment Overdue
Backup Space Billing
Configuration Adjustment Billing
Getting Started
Quickly Creating an Instance
Connecting to a TencentDB for MongoDB Instance
Reading/Writing Database
Operation Guide
Access Management
Instance Management
Node Management
Version Upgrade
Network Configuration
Monitoring
Backup and Rollback
Database Audit
Data Security
SSL Authentication
Log Management
Database Management
Multi-AZ Deployment
Disaster Recovery/Read-Only Instances
Parameter Configuration
Recycle Bin
Task Management
Performance Optimization
Data Migration Guide
Practical Tutorial
Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
Troubleshooting Mongos Load Imbalance in Sharded Cluster
Considerations for Using Shard Clusters
Sample of Reading and Writing Data in MongoDB Instance
Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
Troubleshooting MongoDB Connection Failures
Shard Removal Task: Guide for Confirming the Progress and Troubleshooting Issues
Performance Fine-Tuning
Ops and Development Guide
Development Specifications
Command Support in Sharded Cluster v3.2
Command Support in v3.6
Development Ops
Troubleshooting
Increased Slow Queries
Number of Connections Exceeding Limit
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Backup APIs
Account APIs
Other APIs
Task APIs
Introduction
Data Types
Error Codes
Instance Connection
Shell Connection Sample
PHP Connection Sample
Node.js Connection Sample
Java Connection Sample
Python Connection Sample
Python Read/Write Sample
Go Connection Sample
PHP Reconnection Sample
Product Performance
Test Environment
Test Method
Test Result
FAQs
Cost
Features
Sharded Cluster
Instance
Rollback and Backup
Connection
Data Migration
Others
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Minor Version and Storage Engine

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-02-05 15:14:10

Storage Engine

Starting from version 3.2, TencentDB for MongoDB has upgraded its default storage engine to WiredTiger, fully replacing the earlier MMAPv1 engine. WiredTiger adopts a classic B-Tree architecture and introduces fine-grained concurrency control ranging from document-level to collection-level, significantly improving read-write performance. It also has multiple built-in compression algorithms such as Snappy and Zlib, significantly reducing disk usage and storage costs. Whether in read-intensive, write-intensive, or mixed workload scenarios, WiredTiger delivers better performance and higher storage efficiency to meet various application requirements.

Minor Version Release Notes

Current Latest Version 8.0

Minor Version Number
Addition, Optimization, or Fixing Description
WT.80.12.1
Fixed the security vulnerability CVE-2025-14847.
WT.80.12.0
Compatible with open-source version 8.0

Previous Versions before 8.0

7.0 WiredTiger
6.0 WiredTiger
5.0 WiredTiger
4.4 WiredTiger
4.2 WiredTiger
4.0 WiredTiger
3.6 WiredTiger
3.2 WiredTiger
Minor Version Number
Addition, Optimization, or Fixing Description
WT.70.12.5
Fixed the security vulnerability CVE-2025-14847.
WT.70.12.4
Enhance database audit performance
WT.70.12.3
Supported SQL throttling and Key-based flashback.
WT.70.12.2
Supported enterprise-level features such as database audit, transparent data encryption (TDE), and SSL authentication.
Resolved known issues in the Community Edition.
WT.70.12.1
Optimized the performance.
WT.70.12.0
Supported the 7.0 version.
Minor Version Number
Addition, Optimization, or Fixing Description
WT.60.5.4
Fixed the security vulnerability CVE-2025-14847.
WT.60.5.3
Fixed the issue of errors in the audit configuration information.
Fixed the issue of errors that occurred during backup and database and table rollback.
WT.60.5.2
Supported specifying the flashback log storage path through the flashbacklog.path parameter, which was supported by the Cloud Disk Edition only.
WT.60.5.1
Fixed issues related to the Community Edition.
Fixed the issue of inaccurate monitoring data.
WT.60.5.0
Supported the 6.0 version.
Minor Version
Addition, Optimization, or Fixing Description
WT.50.12.10
Fixed the security vulnerability CVE-2025-14847.
WT.50.12.9
Optimize backup performance
WT.50.12.8
Fixed known issues in the community
WT.50.12.7
Fixed the issue where the listCollections command failed due to excessively large BSON objects.
Optimized the physical backup and rollback process.
WT.50.12.6
Fixed the issue of a parsing failure of the getRestoreInfo command caused by the use-after-free bug.
Fixed the issue of time-series table statistics to ensure all insert operations are accurately recorded and counted.
WT.50.12.1
Supported public network access.
WT.50.12.0
Supported MongoDB 5.0 version.
Minor Version
Addition, Optimization, or Fixing Description
WT.44.13.11
Fixed the security vulnerability CVE-2025-14847.
WT.44.13.10
Fixed known issues in the community
WT.44.13.9
Optimized the physical backup and rollback process.
WT.44.13.8
Supported static encryption.
WT.44.13.4
Supported public network access.
WT.44.13.2
Optimized the isMaster command.
WT.44.13.1
Supported audit and password-free access.
WT.44.13.0
Supported the MongoDB 4.4 version.
Minor Version
Addition, Optimization, or Fixing Description
WT.42.11.21
Fixed the security vulnerability CVE-2025-14847.
WT.42.11.20
Fixed known issues in the community
WT.42.11.19
Optimized the physical backup and rollback process.
WT.42.11.18
Fixed the issue of errors in the audit configuration information.
WT.42.11.17
Optimize audit performance
Supported public network access.
WT.42.11.16
Fixed known issues in the community
WT.42.11.15
Supported custom rule audit for database activities.
Supported database access through SSL authentication.
WT.42.11.14
Improved the stability of the moveChunk kernel.
WT.42.11.13
Supported users to enable the enhanced changeStream mode through commands.
WT.42.11.12
Fixed the issue of errors that occurred when the databases with the same names were created and deleted repeatedly.
Fixed the issue related to changeStream.
WT.42.11.11
Resolved the issue of kernel exceptions that occurred during the applyOps process.
WT.42.11.10
Optimized database audit performance.
WT.42.11.9
Supported database and table rollback through the physical backup method to improve the backup speed.
WT.42.11.8
Optimized the routing information refresh policy.
WT.42.11.7
Optimized the control logic for shard addition.
WT.42.11.6
DDL operations were supported by changeStream.
WT.42.11.5
Optimized kernel parameters to improve performance.
WT.42.11.4
Blocked the high-risk operations of the system.
WT.42.11.3
Fixed the issue of a getMore operation exception.
WT.42.11.2
Supported the maxTimeMS parameter.
WT.42.11.1
Supported the online compact feature.
WT.42.11.0
Supported the MongoDB 4.2 version.
Minor Version
Addition, Optimization, or Fixing Description
WT.40.3.39
Optimize compatibility issues in version 4.2
WT.40.3.38
Optimized the physical backup and rollback process.
WT.40.3.37
Fixed the issue of BatchWriteOp invariance that occurred during MongoDB instance shutdown.
Fixed the issue of node crashes caused by using Flow Control to add nodes.
WT.40.3.35
Supported public network access.
WT.40.3.34
Supported custom rule audit for database activities.
Supported database access through SSL authentication.
WT.40.3.33
Speed limit control was supported by the TTL index.
Supported settings of the expired TTL data cleanup window.
WT.40.3.32
Resolved the issue of stability after physical database and table rollback.
Resolved the issue of memory leakage after connection failures.
WT.40.3.31
Supported SQL traffic throttling.
WT.40.3.30
Supported users to customize the slow query threshold.
WT.40.3.29
Optimized database audit performance.
WT.40.3.28
Optimized the routing refresh policy for sharded clusters.
WT.40.3.27
Supported database and table rollback through the physical backup method.
WT.40.3.26
Optimized the locking logic for write conflict retries to improve performance.
WT.40.3.25
Optimized user permissions to avoid unauthorized operations.
WT.40.3.24
Creation of LSM engine tables and indexes was prohibited.
WT.40.3.23
Optimized the logic of adding shards.
WT.40.3.22
Optimized the lock mechanism.
WT.40.3.21
Optimized the changeStream logic.
WT.40.3.20
Optimized performance.
WT.40.3.19
Optimized the session-related logic.
WT.40.3.18
Optimized the read performance of the secondary database.
WT.40.3.17
Optimized the password-free access logic.
WT.40.3.16
Optimized the logic of collecting monitoring data.
WT.40.3.15
Supported the efficient management of millions of collections.
WT.40.3.14
Optimized the performance of physical backup in scenarios with a large number of files.
WT.40.3.13
Optimized the mongos connection mechanism.
WT.40.3.12
Optimized the routing refresh logic and audit performance.
WT.40.3.11
Enhanced the changeStream capability.
WT.40.3.10
Supported the maxTimeMS parameter.
WT.40.3.9
Supported mongos overload protection.
WT.40.3.8
Supported database audit.
WT.40.3.7
Optimized the session-related logic.
WT.40.3.6
Improved the database connection performance and the database startup performance in scenarios with a large number of files.
WT.40.3.5
Supported password-free access.
WT.40.3.4
Resolved the issue of bloat exceptions in the database disk file.
WT.40.3.3
Supported IPv6.
WT.40.3.2
Supported blocking after the disk is full.
Supported the display of client connection information.
WT.40.3.1
Supported the superGeo command.
Supported the physical backup.
Enriched the monitoring metrics.
WT.40.3.0
Released the MongoDB 4.0 version based on the WiredTiger engine.
Minor Version
Addition, Optimization, or Fixing Description
WT.36.8.13
Resolved the issue of node exceptions caused by excessive memory pressure.
WT.36.8.12
Optimized the password-free access logic.
Optimized the display of the client list.
WT.36.8.11
Optimized the connection performance.
WT.36.8.10
Optimized the session-related logic and the data synchronization logic between nodes.
WT.36.8.9
Supported the physical backup.
WT.36.8.8
Supported the password-free access.
WT.36.8.7
Optimized the Mongos connection pool mechanism.
WT.36.8.6
Optimized the connection logic.
WT.36.8.5
Supported IPv6.
WT.36.8.4
Optimized the logic of monitoring statistics.
WT.36.8.3
Optimized the logic of blocking a disk.
WT.36.8.2
Optimized the connection model.
WT.36.8.1
Optimized the security-related mechanism.
WT.36.8.0
Supported the 3.6 version.
Minor Version
Addition, Optimization, or Fixing Description
WT.32.12.9
Supported setting the maximum timeout duration for requests and creating indexes using the background method by default for instances.
WT.32.12.8
Optimized the Mongos connection pool mechanism of MongoDB.
WT.32.12.7
Supported IPv6 and parameter configurations.
WT.32.12.6
Optimized the kernel connection parameters to improve the performance.
WT.32.12.5
Resolved the issue of kernel probability exceptions.
WT.32.12.4
Supported the superGeoNear command.
WT.32.12.3
Optimized kernel parameters to improve performance.
WT.32.12.2
Supported adjustments of the oplog capacity.
WT.32.12.1
Supported dynamic adjustments of the number of connections.
WT.32.12.0
Supported the MongoDB 3.2 version with the WiredTiger engine.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan