ApsaraDB for MongoDB:Change the configurations of a standalone instance

Billing

For more information, see Configuration change fees.

Limits

• The new storage space that you specify must be greater than or equal to the existing storage space of the standalone instance.
• The storage space of a standalone instance cannot be decreased. To decrease the storage space of a standalone instance, you can create another standalone instance to replace the existing one. For more information, see Other configuration change scenarios and methods.
• The number of nodes, architecture, or storage engine of a standalone instance cannot be changed. For example, a standalone instance cannot be changed into a replica set instance. If you require a different architecture, storage engine, or number of nodes, you can create another instance to replace the existing one. For more information, see Other configuration change scenarios and methods.

Precautions

• The amount of time required to perform a configuration change depends on factors such as the network conditions, task queue status, and data volume. We recommend that you change the configurations of a standalone instance during off-peak hours and make sure that your application is configured to automatically reconnect to the instance.
• During a configuration change, you may experience one or two transient connections. Each transient connection lasts about 30 seconds. To prevent a configuration change from interrupting your workloads, we recommend that you change configurations at a time that has minimal impact on your business.
• Configuration changes do not result in data loss.
• If the minor version of an instance expires or is not included in the maintenance list, ApsaraDB for MongoDB automatically updates the minor version of the instance to the latest version when you perform the following operations. This ensures the performance and stability of the instance.
  • Upgrade the major version of an ApsaraDB for MongoDB instance
  • Data migration
  • Configuration change overview
  • Restore backup data to a new ApsaraDB for MongoDB instance by point in time
  • Restore one or more databases of an ApsaraDB for MongoDB instance

Procedure

1. Log on to the ApsaraDB for MongoDB console.
2. In the left-side navigation pane, click Replica Set Instances.
3. In the upper-left corner of the page, select the resource group and region to which the instance belongs.
4. On the Replica Set Instances page, find the standalone instance.
5. Go to the page on which you can change the configurations of the standalone instance. The available methods to change configurations vary based on the billing method of the instance.
   Subscription

   • Click the icon in the Actions column corresponding to the instance, and select Upgrade or Downgrade.
   • 1. Click the ID of an instance, or click in the Actions column corresponding to the instance and select Manage.
     2. In the Specifications section, click Upgrade or Downgrade in the upper-left corner.

   Pay-as-you-go

   • Click the icon in the Actions column corresponding to the instance, and select Change Configuration.
   • 1. Click the ID of an instance, or click in the Actions column corresponding to the instance and select Manage.
     2. In the Specifications section, click Change Configuration in the upper-left corner.
6. On the Change Configuration page, configure the following parameters.
   Note When you change the value of the Storage Space parameter, you must make sure that the new storage space that you specify is greater than or equal to the existing storage space of the standalone instance. To decrease the storage space of a standalone instance, you can create another standalone instance to replace the existing one. For more information, see Other configuration change scenarios and methods.

   Billing method	Change type	Parameter	Description
   Subscription	Upgrade	Specification	The new specifications of the standalone instance. For more information about the supported specifications of standalone instances, see Instance types.
   		Storage	The new storage space of the standalone instance.
   		Switching Time	The time when you want the system to apply the configuration change. Switch Immediately After Data Migration: ApsaraDB for MongoDB applies the configuration change immediately after the payment is complete. Switch Within Maintenance Window: ApsaraDB for MongoDB applies the configuration change within the maintenance window that you specify. You can also perform the following steps to modify the maintenance window: Click Edit next to Switch Within Maintenance Window. Go to the Basic Information page. In the Specification Information section, click Edit next to Maintenance Period. For more information, see Specify a maintenance window.
   	Downgrade	Specification	The new specifications of the standalone instance. For more information about the supported specifications of standalone instances, see Instance types.
   		Switching Time	The time when you want the system to apply the configuration change. Switch Immediately After Data Migration: ApsaraDB for MongoDB applies the configuration change immediately after the payment is complete. Switch Within Maintenance Window: ApsaraDB for MongoDB applies the configuration change within the maintenance window that you specify. You can also perform the following steps to modify the maintenance window: Click Edit next to Switch Within Maintenance Window. Go to the Basic Information page. In the Specification Information section, click Edit next to Maintenance Period. For more information, see Specify a maintenance window.
   Pay-as-you-go	Upgrade Downgrade	Specification	The new specifications of the standalone instance. For more information about the supported specifications of standalone instances, see Instance types.
   		Storage	The storage capacity that can be selected when you change the configurations. Note The storage capacity of ApsaraDB for MongoDB instances cannot be decreased. To decrease the storage capacity of an ApsaraDB for MongoDB instance, you can create another instance to replace the existing one. For more information, see Other configuration change scenarios and methods.
   		Switching Time	The time when you want the system to apply the configuration change. Switch Immediately After Data Migration: ApsaraDB for MongoDB applies the configuration change immediately after the payment is complete. Switch Within Maintenance Window: ApsaraDB for MongoDB applies the configuration change within the maintenance window that you specify. You can also perform the following steps to modify the maintenance window: Click Edit next to Switch Within Maintenance Window. Go to the Basic Information page. In the Specification Information section, click Edit next to Maintenance Period. For more information, see Specify a maintenance window.

7. Perform the corresponding operations based on the selected billing method.
   • If the billing method is pay-as-you-go, read and select MongoDB Replica Set (Pay-as-you-go) Terms of Service. Then, click Buy Now and the system automatically collects the amount in the next hour.
   • If the billing method is subscription, read and select MongoDB Replica Set (Subscription) Terms of Service, and click Buy Now. Then, complete the payment on the Purchase page.
   When the configuration change is being applied, the standalone instance is in the Changing Configuration state. When the configuration change is complete, the state of the instance changes to Running.

Related API operations