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

Restarting Instance

PDF
Focus Mode
Font Size
Last updated: 2025-10-20 17:09:42
If the number of connections to an instance reaches the threshold or the instance has performance problems, you need to restart it manually. This document describes how to restart a replica set or sharded instance.

Overview

When the system becomes completely unavailable due to a high load, you can restart it to resume node operations. Due to the architecture of the TencentDB for MongoDB instance, instance restart divides into mongos restart and mongod restart.
mongos is a routing service configured for MongoDB sharding. It processes query requests from the application layer and determines the location of data in a sharded cluster.
mongod is the primary daemon process for the MongoDB system. It handles data requests, manages data access, and performs background management operations.

Version Description

The MongoDB version 3.2 and later support restarting instance.
The architecture of MongoDB 4.0 replica set instance is simplified, where the mongos component is removed; therefore, instance restart doesn't involve mongos restart.

Note

During restart, there may be one or two momentary disconnections for around 10s each. We recommend that you configure an automatic reconnection feature for your application.
You cannot cancel an ongoing restart operation; therefore, proceed with caution.

Prerequisites

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

Directions

Restarting one instance

2. In the MongoDB drop-down list on the left sidebar, select Replica Set Instance or Shard 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. On the row of the target instance, click More > Restart in the Operation column.


6. In the Restart MongoDB window, click View Details to confirm the information of the instance to be restarted.
7. Select the components to be restarted and click OK.
8. In the instance list, you can see that the instance enters the Restarting status. Wait for the task to be completed.

Restarting multiple instances

1. In the instance list, select the instances to be restarted.
2. Above the instance list, click Restart.
3. In the Restart MongoDB window, click View Details to confirm the information of all the instances to be restarted.
4. Select the components to be restarted and click OK.

Help and Support

Was this page helpful?

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

Feedback