- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Node Overview
- Viewing Node Information
- Adjusting Mongod Node Specification
- Adding Secondary Node
- Deleting Secondary Node
- Adding Read-Only Node
- Adjusting Shard Quantity
- Adjusting Mongos Node Specification
- Adding Mongos Node
- Enabling Mongos Access Address
- Promoting Secondary Node to Primary Node
- Restarting a Node
- Version Upgrade
- Network Configuration
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Disaster Recovery/Read-Only Instances
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Creating a DTS Migration Task
- Migration Overview
- Supported Capabilities
- User Guide
- Migration Operation Guide
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- Consistency Check After Migration
- Creating MongoDB Data Subscription
- Creating a DTS Migration Task
- 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
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- API Category
- Making API Requests
- Backup APIs
- Introduction
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- Product Performance
- FAQs
- Service Agreement
- Glossary
- Contact Us
- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Node Overview
- Viewing Node Information
- Adjusting Mongod Node Specification
- Adding Secondary Node
- Deleting Secondary Node
- Adding Read-Only Node
- Adjusting Shard Quantity
- Adjusting Mongos Node Specification
- Adding Mongos Node
- Enabling Mongos Access Address
- Promoting Secondary Node to Primary Node
- Restarting a Node
- Version Upgrade
- Network Configuration
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Disaster Recovery/Read-Only Instances
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Creating a DTS Migration Task
- Migration Overview
- Supported Capabilities
- User Guide
- Migration Operation Guide
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- Consistency Check After Migration
- Creating MongoDB Data Subscription
- Creating a DTS Migration Task
- 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
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- API Category
- Making API Requests
- Backup APIs
- Introduction
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- Product Performance
- FAQs
- Service Agreement
- Glossary
- Contact Us
This document describes the specifications of replica set and sharded cluster instances supported by TencentDB for MongoDB to help you choose a specification suitable for your business.
Replica Set
Replica quantity
Primary and secondary nodes: A one-primary-two-secondary architecture with three storage nodes is adopted by default. You can select five (one-primary-four-secondary) or seven (one-primary-six-secondary) nodes. Currently, you cannot customize the number of replicas.
Read-only nodes: You can configure 0–5 secondary nodes as read-only nodes.
Mongod specification
General Edition
Note:
The maximum number of connections for a 3-node replica set instance refers to the standard maximum connections for each specification. The single-node connection limit is the maximum limit that can be increased to.
CPU per Node | Memory per Node (GB) | Disk Capacity per Node (GB) | Maximum Connections to Three Nodes | Single-Node Connection Limit (The actual limit does not exceed the maximum connections for the instance.) |
2 cores | 4 GB | Default: 250 GB; range: [100,500] | 3000 | 10,000 |
4 cores | 8 GB | Default: 500 GB; range: [150,1000] | 6000 | |
6 cores | 16 GB | Default: 750 GB; range: [250,1500] | 9000 | |
12 cores | 32 GB | Default: 1500 GB; range: [500,6000] | 12000 | 15,000 |
24 cores | 64 GB | Default: 2500 GB; range: [800,5000] | 18000 | |
24 cores | 128 GB | Default: 3000 GB; range: [1500,5000] | 21000 | |
32 cores | 240 GB | Default: 4000 GB; range: [1500,6000] | 42000 | 20,000 |
48 cores | 512 GB | Default: 4000 GB; range: [1500,6000] | 60000 | |
Cloud Edition
CPU per Node | Memory per Node (GB) | Disk Capacity per Node (GB) | Maximum Connections for a 3-node Instance | Single-Node Connection Limit
(The actual limit does not exceed the maximum connections for the instance.) |
2 cores | 4 GB | Default: 250 GB; range: [10,6000] | 3000 | 10,000 |
4 cores | 8 GB | Default: 500 GB; range: [10,6000] | 6000 | |
6 cores | 16 GB | Default: 750 GB; range: [10,6000] | 9000 | |
12 cores | 32 GB | Default: 1500 GB; range: [10,6000] | 12,000 | 15,000 |
24 cores | 64 GB | Default: 2500 GB; range: [10,6000] | 18,000 | |
24 cores | 128 GB | Default: 3000 GB; range: [10,6000] | 21,000 | |
Sharded Cluster
Mongod specification
General Edition
CPU per Node | Memory per Shard (GB) | Disk Capacity per Shard (GB) |
2 cores | 4 GB | Default: 250 GB; range: [100,500] |
4 cores | 8 GB | Default: 500 GB; range: [150,1000] |
6 cores | 16 GB | Default: 750 GB; range: [250,1500] |
12 cores | 32 GB | Default: 1500 GB; range: [500,6000] |
24 cores | 64 GB | Default: 2500 GB; range: [800,5000] |
24 cores | 128 GB | Default: 3000 GB; range: [1500,5000] |
32 cores | 240 GB | Default: 4000 GB; range: [1500,6000] |
48 cores | 512 GB | Default: 4000 GB; range: [1500,6000] |
Cloud Edition
CPU per Node | Memory per Node (GB) | Disk Capacity per Node (GB) |
2 cores | 4 GB | Default: 250 GB; range: [10,6000] |
4 cores | 8 GB | Default: 500 GB; range: [10,6000] |
6 cores | 16 GB | Default: 750 GB; range: [10,6000] |
24 cores | 128 GB | Default: 3000 GB; range: [100,6000] |
Mongod shard quantity
Value range of the number of shards: [2,36].
Node quantity per mongod shard
Primary and secondary nodes: A one-primary-two-secondary architecture with three storage nodes is adopted by default. You can select five (one-primary-four-secondary) or seven (one-primary-six-secondary) nodes. Currently, you cannot customize the number of replicas.
Read-only nodes: You can configure 0–5 secondary nodes as read-only nodes.
Mongos specification
A single-AZ deployed instance can contain 3–32 nodes.
A multi-AZ deployed instance can contain 6–32 instances.
Mongos Specification | Maximum Connections per Mongos Node |
1-core 2 GB MEM | 1000 |
2-core 4 GB MEM | 2000 |
4-core 8 GB MEM | 4000 |
8-core 16 GB MEM | 8000 |
16-core 32 GB MEM | 16000 |
configServer specification
The default configServer specification is 1-core 2 GB with 20 GB storage and three replicas, which cannot be modified.
User Name for Instance Connection
TencentDB for MongoDB comes with a default user: "mongouser". It supports the SCRAM-SHA-1 authentication mechanism, and its role is readWriteAnyDatabase+dbAdmin. You can use it to read and write any database, but are not permitted to perform high-risk operations.
TencentDB for MongoDB v3.2 supports another default user: "rwuser". It uses the MONGODB-CR authentication mechanism which, however, has been no longer supported by MongoDB. We recommend that you use the "mongouser" to connect to your instance.
You can also manage your account and permissions as needed in the TencentDB for MongoDB console.
Avoiding Filling Up Disk
If the disk usage of an instance has reached 100%, you cannot write to it. You need to adjust the instance specification in time or contact us for assistance. For more information, see Adjusting Instance Specification.
Yes
No
Was this page helpful?