This topic describes how to change the configurations of an existing instance to better meet your needs by using the corresponding features in the ApsaraDB for MongoDB console.
Configuration change methods
Configuration change methods and change items vary based on instance categories. The following table describes the configuration change methods and change items for different categories of instances.
Configuration change method | Billing method | Change type | Change item |
---|---|---|---|
Change the configurations of a standalone instance | Subscription | Upgrade | The Specifications and Storage configurations of an instance can be changed. |
Downgrade | The Specifications configuration of an instance can be changed. | ||
Pay-as-you-go |
| The Specifications and Storage configurations of an instance can be changed. Note
| |
Change the configurations of a replica set instance | Subscription | Upgrade | The Active-standby Nodes, Read-only Nodes, Specifications, and Storage configurations of an instance can be changed. Note
|
Downgrade | The Active-standby Nodes, Read-only Nodes, and Specifications configurations of an instance can be changed. Note The Active-standby Nodes and Read-only Nodes configurations cannot be changed for instances that run MongoDB 5.0 or 4.4. | ||
Pay-as-you-go |
| The Active-standby Nodes, Read-only Nodes, Specifications, and Storage configurations of an instance can be changed. Note
| |
Overview | Subscription | Add a mongos node | When you add a mongos node, you can set Instance Specifications and Quantity. Note A maximum of 32 mongos nodes can be added to each sharded cluster instance. If the sharded cluster instance already has three mongos nodes and you want to add more mongos nodes, you can add a maximum of 29 mongos nodes to the sharded cluster instance. |
Add a shard node | When you add a shard node, you can set Instance Specifications, Quantity, Storage Capacity, and Read-only Nodes. Note
| ||
Change the configurations of one or more mongos nodes | The Instance Specifications configurations of one or more mongos nodes can be changed. | ||
Change the configurations of one or more shard nodes | The Instance Specifications, Storage Capacity, and Read-only Nodes configurations of one or more shard nodes can be changed. Note
| ||
Pay-as-you-go | Add a mongos node | When you add a mongos node, you can set Instance Specifications and Quantity. Note A maximum of 32 mongos nodes can be added to each sharded cluster instance. If the sharded cluster instance already has three mongos nodes and you want to add more mongos nodes, you can add a maximum of 29 mongos nodes to the sharded cluster instance. | |
Add a shard node | When you add a shard node, you can set Instance Specifications, Quantity, and Storage Capacity. Note
| ||
Change the configurations of one or more mongos nodes | The Instance Specifications configurations of one or more mongos nodes can be changed. | ||
Change the configurations of one or more shard nodes | The Instance Specifications and Storage Capacity configurations of one or more shard nodes can be changed. Note
| ||
Release a mongos or shard node | You can manually release a mongos or shard node. Note
|
Other configuration change scenarios and methods
You may encounter the following configuration change scenarios:
- Downgrade the storage capacity of an instance or a shard node.
- Add the number of nodes for a standalone instance.
- Change the architecture of an instance.
- Change the storage engine from RocksDB or TerarkDB to WiredTiger.
When you encounter the preceding scenarios, you can perform the following steps to change the configurations:
- Create an instance. For more information, see Create a standalone instance, Create a replica set instance, or Create a sharded cluster instance. Note
- If you want to decrease the storage capacity by creating another instance, the storage capacity of the new instance must be greater than the amount of capacity used by the source instance.
- If you want to change the number of nodes by creating another instance, you must create a replica set instance.
- If you want to change the instance architecture by creating another instance, you must choose an instance category specific to the desired architecture. For more information about the instance architecture, see Architecture of ApsaraDB for MongoDB.
- In backup and restoration scenarios, you can clone an instance to create another instance. For more information, see Restore backup data to a new ApsaraDB for MongoDB instance by point in time or Restore backup data to a new ApsaraDB for MongoDB instance by backup point.
- Migrate the data of the source instance to the new instance. For more information, see Overview.
- After you verify functionality of the new instance, switch business from the source instance to the new instance.
- Optional: If you no longer need the source instance, release the instance.
- For a subscription instance, you cannot manually release the instance.
- For a pay-as-you-go instance, you can manually release the instance. For more information, see Release an instance or a node.
References
For more information about MongoDB versions, storage engines, and the relationship between MongoDB versions and storage engines, see MongoDB versions and storage engines.
For more information about how to upgrade the MongoDB version of an instance, see Upgrade the major version of an ApsaraDB for MongoDB instance.