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 a Node

PDF
Focus Mode
Font Size
Last updated: 2024-10-10 11:47:15

Overview

In daily Ops, restarting nodes helps free up memory or clear caches, optimizing resource usage. When a node experiences a failure, restarting it can assist in restoring service.

Must-Knows

Restarting a node will disconnect existing connections, so ensure that your application has a reconnection mechanism in place.
Restarting the primary node will trigger a primary-secondary switch, and there is a risk of data loss if unsynchronized data has not been replicated to the secondary node. Assess the risks carefully.

Prerequisite

Instance status should be Running.

Restarting Mongod Node

1. Log in to the MongoDB Console.
2. In the left sidebar, choose Replica Set Instance or Shard Instance from the MongoDB dropdown.
3. At the top of the Instance List page on the right, select the region.
4. In the instance list, find the target instance for which you want to view the node.
5. Click the instance ID to enter the Instance Details page, and click the Node Management tab.
6. On the Node Management page, under the Mongod Node tab, locate the node you want to restart in the node list.
7. In the Operation column, click Restart.
Replica set

Sharded instance

8. In the Restart Mongod Node popup window, view the must-knows, check the box for Confirm the risk of restarting the node, and click OK.

9. Wait for the task to be completed.

Restarting ConfigServer Node

1. Log in to the MongoDB Console.
2. In the left sidebar, select Replica Set Instance or Shard Instance from the MongoDB dropdown.
3. At the top of the Instance List page on the right, select the region.
4. In the instance list, find the target instance for which you want to view the node.
5. Click the instance ID to enter the Instance Details page, and click the Node Management tab.
6. On the Node Management page, under the ConfigServer Node tab, locate the node you want to restart in the node list.
7. In the Operation column, click Restart.

Help and Support

Was this page helpful?

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

Feedback