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 action Change item
Change the specifications of a standalone instance Subscription Upgrade configurations. The Specification and Storage Space configurations of an instance can be changed.
Downgrade configurations. The Specification configuration of an instance can be changed.
Pay-as-you-go
  • Upgrade configurations.
  • Downgrade configurations.
The Specification and Storage Space configurations of an instance can be changed.
Note
  • When you change the Storage Space configuration, you must adjust the Storage Space slider to a value greater than the amount of space occupied by the current instance.
  • The storage space of ApsaraDB for MongoDB instances cannot be decreased. To decrease the storage space of an ApsaraDB for MongoDB instance, you can create another instance. For more information, see Other configuration change scenarios and methods.
Change the configurations of replica set instances Subscription Upgrade configurations. The Nodes, Specification, and Storage Space configurations of an instance can be changed.
Note When you change the Storage Space configuration, you must adjust the Storage Space slider to a value greater than the amount of space occupied by the current instance.
Downgrade configurations. The Nodes and Specification configurations of an instance can be changed.
Pay-as-you-go
  • Upgrade configurations.
  • Downgrade configurations.
The Nodes, Specification, and Storage Space configurations of an instance can be changed.
Note
  • When you change the Storage Space configuration, you must adjust the Storage Space slider to a value greater than the amount of space occupied by the current instance.
  • The storage space of ApsaraDB for MongoDB instances cannot be decreased. To decrease the storage space of an ApsaraDB for MongoDB instance, you can create another instance. For more information, see Other configuration change scenarios and methods.
Change the specifications of a sharded cluster instance Subscription Add mongos nodes. When you add a mongos node, you can set Instance Specifications.
Add shard nodes. When you add a shard node, you can set Instance Specifications, Storage Capacity, and Read-only Nodes.
Note
  • The Instance Specifications, Storage Capacity, and Read-only Nodes values of the added shard node must be greater than or equal to the highest values among existing shard nodes.
  • The storage space of shard nodes in an ApsaraDB for MongoDB sharded cluster instance cannot be decreased. To decrease the storage space of a shard node, you can create another instance. For more information, see Other configuration change scenarios and methods.
Change mongos node configurations. The Instance Specifications configuration of a mongos node can be changed.
Change shard node configurations. The Instance Specifications, Storage Capacity, and Read-only Nodes configurations of a shard node can be changed.
Note
  • When you change the Storage Capacity configuration, you must adjust the Storage Capacity slider to a value greater than the amount of space occupied by the current largest instance.
  • The storage space of shard nodes in an ApsaraDB for MongoDB sharded cluster instance cannot be decreased. To decrease the storage space of a shard node, you can create another instance. For more information, see Other configuration change scenarios and methods.
Pay-as-you-go Add mongos nodes. When you add a mongos node, you can set Instance Specifications.
Add shard nodes. When you add a shard node, you can set Instance Specifications and Storage Capacity.
Note
  • When you change the Storage Space configuration, you must adjust the Storage Space slider to a value greater than the amount of space occupied by the current instance.
  • The storage space of shard nodes in an ApsaraDB for MongoDB sharded cluster instance cannot be decreased. To decrease the storage space of a shard node, you can create another instance. For more information, see Other configuration change scenarios and methods.
Change mongos node configurations. The Instance Specifications configuration of a mongos node can be changed.
Change shard node configurations. The Instance Specifications and Storage Capacity configurations of a shard node can be changed.
Note
  • When you change the Storage Space configuration, you must adjust the Storage Space slider to a value greater than the amount of space occupied by the current instance.
  • The storage space of shard nodes in an ApsaraDB for MongoDB sharded cluster instance cannot be decreased. To decrease the storage space of a shard node, you can create another instance. For more information, see Other configuration change scenarios and methods.

Other configuration change scenarios and methods

You may encounter the following configuration change scenarios:
  • Downgrade the storage space 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.
  • Change the instance billing method from subscription to pay-as-you-go.
When you encounter the preceding scenarios, you can use the following methods to change the configurations:
  1. 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 space by creating another instance, the storage space of the new instance must be greater than the amount of space used by the current 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.
    • If you want to change the instance billing method from subscription to pay-as-you-go by creating another instance, you must set the billing method of the new instance to pay-as-you-go.
    • In backup and restoration scenarios, you can clone an instance to create another instance. For more information, see Restore data to a new ApsaraDB for MongoDB instance by point in time or Create an instance from a backup.
  2. Migrate the data of the source instance to the new instance. For more information, see Overview.
  3. After you verify functionality of the new instance, switch business from the source instance to the new instance.
  4. Optional:If you no longer need the source instance, release the instance by using one of the following methods:
    • For a subscription instance, you can release the instance by submitting a ticket. To submit a ticket, go to the New Ticket page.
    • For a pay-as-you-go instance, you can manually release the instance. For more information, see Release an ApsaraDB for MongoDB instance.

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 MongoDB versions.