This topic describes how to change the configurations of a standalone instance. If the specifications of a standalone instance are higher or lower than the specifications that are required for your business, you can change the configurations of the instance based on your business requirements.

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.
  • To ensure better performance and stability of the instance, the system will upgrade the minor version to the latest version by default. If the minor version of your instance expires or is not included in the maintenance list and the instance is upgraded, migrated, changed, Created from a backup, Created by point-in-time, or performed Restore one or more databases of an ApsaraDB for MongoDB instance.

Procedure

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Replica Set Instances.
  4. On the Replica Set Instances page, find the standalone instance whose configurations you want to change.
  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 More icon icon in the Actions column corresponding to the instance, and select Upgrade or Downgrade.
    • Click the instance ID. In the Basic Information section, click Upgrade or Downgrade.
    Pay-as-you-go
    • Click the More icon icon in the Actions column corresponding to the instance, and select Change Configuration.
    • Click the instance ID. In the Basic Information section, click Change Configuration.
  6. 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 action 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 Space 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 view the maintenance window. You can also change the maintenance window by using one of the following methods:
      • Click Modify 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 period.
    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 view the maintenance window. You can also change the maintenance window by using one of the following methods:
      • Click Modify 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 period.
    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 Space The new storage space of the standalone instance.
    Note 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 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 view the maintenance window. You can also change the maintenance window by using one of the following methods:
      • Click Modify 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 period.
  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

Operation Description
ModifyDBInstanceSpec Changes the specifications or storage space of a standalone, replica set, or serverless instance.