- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Access Management
- Instance Management
- Node Management
- Version Upgrade
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Public Network Access
- Disaster Recovery/Read-Only Instances
- Parameter Configuration
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Best Practice
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Troubleshooting Excessive Slow Queries
- Fixing High CPU Utilization in MongoDB Instance Based on DBbrain
- Troubleshooting Excessive Connections
- Troubleshooting High Request Latency Based on Slow Log
- Troubleshooting High CPU Utilization
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Export and Import
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Backup APIs
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- 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
- Version Upgrade
- Monitoring
- Backup and Rollback
- Data Security
- SSL Authentication
- Database Management
- Multi-AZ Deployment
- Public Network Access
- Disaster Recovery/Read-Only Instances
- Parameter Configuration
- Recycle Bin
- Task Management
- Performance Optimization
- Data Migration Guide
- Best Practice
- Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
- Troubleshooting Mongos Load Imbalance in Sharded Cluster
- Troubleshooting Excessive Slow Queries
- Fixing High CPU Utilization in MongoDB Instance Based on DBbrain
- Troubleshooting Excessive Connections
- Troubleshooting High Request Latency Based on Slow Log
- Troubleshooting High CPU Utilization
- Considerations for Using Shard Clusters
- Sample of Reading and Writing Data in MongoDB Instance
- Export and Import
- Troubleshooting MongoDB Connection Failures
- Performance Fine-Tuning
- Ops and Development Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenameInstance
- OfflineIsolatedDBInstance
- ModifyDBInstanceSpec
- IsolateDBInstance
- DescribeSpecInfo
- DescribeDBInstances
- DescribeClientConnections
- CreateDBInstanceHour
- AssignProject
- RenewDBInstances
- DescribeSlowLogs
- DescribeSlowLogPatterns
- InquirePriceRenewDBInstances
- InquirePriceModifyDBInstanceSpec
- InquirePriceCreateDBInstances
- DescribeDBInstanceDeal
- DescribeSecurityGroup
- DescribeInstanceParams
- ModifyDBInstanceSecurityGroup
- ModifyDBInstanceNetworkAddress
- Backup APIs
- Account APIs
- Task APIs
- Other APIs
- Data Types
- Error Codes
- Instance Connection
- 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
CPU per Node | Memory per Node (GB) | Disk Capacity per Node (GB) | Maximum Connections to Three Nodes |
2 cores | 4 GB | Default: 250 GB; range: [100,500] | 3000 |
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 |
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 |
48 cores | 512 GB | Default: 4000 GB; range: [1500,6000] | 60000 |
Sharded Cluster
Mongod specification
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] |
Mongod shard quantity
Value range of the number of shards: [2,20].
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?