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

Adding Mongos Node

PDF
Focus Mode
Font Size
Last updated: 2025-02-06 17:57:57

Overview

You can add more mongos nodes to increase the maximum number of connections to the database instance.

Version requirements

Sharded clusters in version 4.0 and later currently support adding new Mongos nodes.

Instructions

After you add a mongos node, the system will automatically bind an IP address to it and enable the connection string for mongos access. Then, you can directly copy the connection string in the Network section on the Instance Details page.

Prerequisites

Instance type: Sharded cluster instance.
Instance status: Running.
The CPU performance and memory capacity of the mongos nodes are insufficient and need to be upgraded.

Directions

2. In the MongoDB drop-down list on the left sidebar, select Shard Instance.
3. Above the Instance List on the right, select the region.
4. In the Instance List, find the target instance.
5. Click the Instance ID to enter the Instance Details page and click the Node Management tab.
6. On the Node Management tab, click the Mongos Node tab.
7. On the Mongos Node tab, click Add Mongos Node.
The instance nodes are in the same AZ:

The instance nodes are in different AZs:

Parameter
Description
Instance ID/Name
The unique ID and name of the instance.
AZ
The AZ where the instance resides. This parameter will be displayed if the instance nodes are in the same AZ.
Mongos Count
The current number of mongos nodes configured for the instance. This parameter will be displayed if the instance nodes are in the same AZ.
Mongos Specs
Specification of mongos nodes, including the number of CPU cores, memory, and maximum number of connections.
Add Mongos Node
Select the number of mongos nodes to be added. An instance can have up to 48 mongos nodes.
Total Fees
Fees after specification adjustment.
In pay-as-you-go billing mode, fees are charged hourly by the new specification in three billing tiers.
Compare
You can compare the specification, number of nodes in the AZ, and maximum numbers of connections before and after mongos nodes are added to assess whether the new specification meets your needs.
8. After confirming that everything is correct, click OK.

Help and Support

Was this page helpful?

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

Feedback