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

Setting Instance Maintenance Period

PDF
Focus Mode
Font Size
Last updated: 2025-10-20 17:23:38
TencentDB for MongoDB allows you to adjust the instance maintenance period in the console to meet the changes in your business requirements.

Overview

The maintenance period is crucial for ensuring the stability of your TencentDB for MongoDB instance. During this period, the backend system performs necessary maintenance operations on your instance. To minimize the potential impact on your business, we recommend you set an acceptable maintenance period, preferably during off-peak hours. This will help mitigate any disruptions to your business operations.
In addition, we also recommend you perform operations involving data migration, such as adjusting the memory specification or AZ of mongod or mongos nodes, during the maintenance period. Taking the database instance AZ change as an example, as the full and incremental data needs to be synced from the original AZ to the new AZ, data migration will be involved. After the AZ is changed, a momentary disconnection from the database may occur. When the task is initiated, the Switch Time can be selected as During maintenance period, so that the instance data migration will be started during the next maintenance period after the data sync is completed.
Note:
Before maintenance is carried out for TencentDB for MongoDB, notifications will be sent to the contacts configured in your Tencent Cloud account through SMS and email.

Version Description

Currently, TencentDB for MongoDB versions 3.2, 3.6, 4.0, 4.2, 4.4, 5.0, and 6.0 support maintenance period configuration.

Prerequisites

You have created a TencentDB for MongoDB instance. For more information, see Creating TencentDB for MongoDB Instance.
The TencentDB for MongoDB replica set or sharded cluster instance is in Running status.

Directions

2. In the MongoDB drop-down list on the left sidebar, select Replica Set Instance or Sharded Instance. The directions for replica set instances and sharded cluster instances are similar.
3. Above the Instance List on the right, select the region.
4. In the instance list, find the target instance.
5. Click the target instance ID to enter the Instance Details page.
6. On the Instance Details page, click Modify on the right of Maintenance Time.

7. In the Modify Maintenance Time window, set Start Time and Duration.

8. Click OK. You can view the newly set maintenance time on the Instance Details page.

Help and Support

Was this page helpful?

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

Feedback