Overview
If the specification of your purchased TencentDB for MongoDB instance doesn't meet your current business requirements, whether it's below or above, you can easily adjust it according to your actual business conditions (at the initial stage, at the rapid development stage, during peak hours, or during off-peak hours), so as to better meet your needs such as full utilization of resources and real-time cost optimization.
Adjusting the specification
The memory and CPU cores of mongod and mongos nodes are in fixed combinations, and the disk capacity has a corresponding value range. For example, if the specification of a mongod node is 2-core 4 GB MEM, then the disk capacity can range from 100 to 500 GB.
Mongod replica secondary nodes: You have the option to choose between 3 nodes (one-primary-two-secondary), five (one-primary-four-secondary), or seven (one-primary-six-secondary) nodes. Currently, you cannot customize the number of secondary nodes.
The numbers of mongos nodes supported by single-AZ deployed and multi-AZ deployed instances are different. A single-AZ deployed instance can contain 3–32 nodes, while a multi-AZ deployed instance can contain 6–32 nodes.
You can select a specification based on your business conditions as described in Product Specifications first. Then, select an adjustment type and make adjustments based on the following table. |
| You can adjust the memory, disk capacity, and oplog capacity of a mongod node. |
| You can add or remove secondary nodes in both replica set and sharded cluster. You have the option to choose between 3 nodes (one-primary-two-secondary), five (one-primary-four-secondary), or seven (one-primary-six-secondary) nodes. Currently, you cannot customize the number of secondary nodes. |
| You can add or remove mongod shards in a sharded cluster. |
| You can adjust the CPU cores and memory of mongos nodes in a sharded cluster. |
| You can add mongos nodes in a sharded cluster. |
| You can add 0 to 5 read-only nodes. |