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
DokumentasiTencentDB for MongoDBProduct IntroductionProduct SpecificationsSharded Instance Specifications

Sharded Instance Specifications

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-11-25 16:04:57

Mongod Specifications

General Edition

CPU Core per Node
Memory per Shard (GB)
Disk Capacity per Shard (GB)
2 cores
4GB
Default value: 250 GB; value range: [100, 500]
4 cores
8GB
Default value: 500 GB; value range: [150, 1000]
6 cores
16GB
Default value: 750 GB; value range: [250, 1500]
12 cores
32GB
Default value: 1500 GB; value range: [500, 4000]
24 cores
64GB
Default value: 2500 GB; value range: [800, 5000]
24 cores
128GB
Default value: 3000GB; value range: [1500, 5000]
32 cores
240GB
Default value: 4000 GB; value range: [1500, 6000]
48 cores
512GB
Default value: 4000 GB; value range: [1500, 6000]

Cloud Disk Edition

CPU Core per Node
Memory per Node (GB)
Disk Capacity per Node (GB)
2 cores
4GB
Default value: 250 GB; value range: [10, 6000]
4 cores
8GB
Default value: 500 GB; value range: [10, 6000]
6 cores
16GB
Default value: 750 GB; value range: [10, 6000]
12 cores
32GB
Default value: 1500 GB; value range: [100, 6000]

Number of Mongod Shards

The value range of the shard number is [2, 36].
Number of nodes per Mongod shard
Primary/Secondary node: The default value is 3 storage nodes (1 primary node and 2 secondary nodes), which forms an architecture consisting of 1 primary node and 2 secondary nodes. Options of 5 nodes (1 primary node and 4 secondary nodes) and 7 nodes (1 primary node and 6 secondary nodes) are also supported, but the number of replicas cannot be customized currently.
Read-only node: It is supported to configure secondary nodes as read-only nodes. The value range is [0, 5].

Mongos Specifications

- For instances in single-AZ deployment mode, the value range is [3,32].
- For instances in multi-AZ deployment mode, the value range is [6,32].
Mongos Specification
Number of Connections per Mongos Node
1 core and 2 GB
1000
2 cores and 4 GB
2000
4 cores and 8 GB
4000
8 cores and 16 GB
8000
16 cores and 32 GB
16000

ConfigServer Specification

The default specification of ConfigServer is 1 core, 2 GB, and 20 GB storage. The default replica value is 3, and it cannot be modified.

Avoiding Full Disk Usage

When the disk of an instance is full, the write operation is prohibited. Adjust the instance configuration promptly based on your business situation. For details about adjusting the instance configuration, see Adjusting Instance Specifications. If a disk is full and gets blocked, contact us for help.
Topik sebelumnya: Replica Set SpecificationsTopik selanjutnya: Major Version Feature Details

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan