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

Version Upgrade

PDF
Focus Mode
Font Size
Last updated: 2026-03-05 18:59:59

Overview

TencentDB for MongoDB supports major and minor version upgrades, enabling you to benefit from improved stability, security, and new features. You can upgrade the database version of your instance to a later version based on your business needs.
Major version upgrade: refers to a major version change (such as 4.0 → 4.2), which typically introducing new features, performance optimization, and other significant improvements. For the features supported by each version, see Major Version Feature Details.
Minor version upgrade: typically refers to a patch version update of the storage engine (such as WT.40.3.34 → WT.40.3.35), which primarily includs bug fixes, security patches, and minor performance improvements. For minor version update records, see Minor Versions and Storage Engine.

Upgrade Mechanism

Upgrade Path: Major version upgrades must be performed sequentially and do not support skipping versions. The supported upgrade path is: 3.6 → 4.0 → 4.2 → 4.4 → 5.0→ 6.0→ 7.0→ 8.0.
Automatic Version Upgrade Detection: The system automatically detects and notifies you of available version upgrades, and does not support custom target versions.
Note:
The upgrade process is fully automated. It involves a primary/secondary switchover and several momentary disconnections, each typically lasting a few seconds. It is recommended to perform the upgrade during off-peak hours.

Prerequisites

The instance is not a read-only or disaster recovery instance.
The instance to be upgraded is in a normal state (Running).
The target version is confirmed.

Operation Steps

2. In the MongoDB drop-down list on the left sidebar, select Replica Set Instance or Shard Instance. The operations for Replica Set Instance and Sharded Instance are similar.
3. Select Region at the top of the Instance List page on the right.
4. In the instance list, find the instance that needs a version upgrade.
5. In the Instance ID / Name column of the target instance, click the Instance ID to go to the Instance Details page.
6. In the Instance Details page's Specs Info section, upgrade the major or minor version of the instance.
If the instance is version 3.6, click Upgrade to v4.0 after Version and Engine to upgrade the version from 3.6 to 4.0.
If the instance is version 4.0, click Upgrade to v4.2 after Version and Engine to upgrade the version from 4.0 to 4.2, and so on.
Click Upgrade Minor Version to perform a minor version upgrade, which will be updated to the latest minor version by default.

7. In the Upgrade Version dialog box, read the prompt information, confirm the upgrade, and click OK.
8. Wait for the upgrade task to complete. Once the instance status returns to Running, you will see the version information has been updated.
Note:
The upgrade will be completed within a few minutes. Please wait patiently.

Related APIs

API
Description
Upgrade the instance kernel minor version number
Upgrading the database version

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback