tencent cloud

TencentDB for MongoDB

DokumentasiTencentDB for MongoDBOperation GuideInstance ManagementAdjusting Instance Specification

Adjusting Instance Specification

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-04-17 17:36:16

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

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.
Modify node type
Specification Constraints
Mongod Configuration
Memory size and CPU cores are fixed in combination and cannot be adjusted separately.
Disk capacity needs to be adjusted within the range supported by the corresponding specification. For example, when the specification is 2 cores and 4GB, the disk capacity range may be [100, 500]GB.
The number of secondary nodes supports the following fixed combinations, and custom configurations are currently not supported:
3 nodes (1 primary node and 2 secondary nodes)
5 nodes (1 primary node and 4 secondary nodes)
7 nodes (1 primary node and 6 secondary nodes)
Mongos Configuration
The number of nodes varies based on the AZ allocation mode:
Single-AZ deployment: supports [3, 32] nodes.
multi-AZ deployment: supports [6, 32] nodes.

Change Operation Overview

The following table lists the major configuration adjustment operations supported by TencentDB for MongoDB and their specific details. You can select the appropriate operations based on your business needs.
Change operation
Operation Details
Adjust the number of CPU cores, memory, disk capacity, and Oplog capacity for Mongod nodes to enhance data storage and processing capabilities, where CPU cores and memory are fixed in pairing.
Adjust Oplog storage capacity to meet the storage requirements for data change records. Oplog occupies 10% of the Mongod disk capacity by default.
Increase the number of secondary nodes in the replica set to scale read performance, enhance high availability, or achieve resource isolation.
Reduce the number of secondary nodes in the replica set to lower resource costs or adjust the cluster architecture.
Increase the number of Mongod shards in the sharded cluster to expand data-bearing capacity and processing performance.
Reduce the number of Mongod shards in the sharded cluster to release resources and adjust the cluster scale to match the business load.
Adjust the number of CPU cores and memory for Mongos nodes in the sharded cluster to enhance request routing processing capability.
Adjust the number of Mongos nodes in the sharded cluster to increase or decrease as needed, flexibly adapting to business traffic fluctuations.
Increase the quantity of read-only nodes to scale read capacity. Value range: 0–5.
Topik sebelumnya: Viewing Instance DetailsTopik selanjutnya: Accessing Instance Without Authentication

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan