ApsaraDB for Redis supports the subscription and pay-as-you-go billing methods. You can change the billing method from pay-as-you-go to subscription. Both billing methods allow you to modify the specifications of an instance.

Background

Both the pay-as-you-go and subscription billing methods allow you to upgrade or downgrade instances at any time. You can change the architecture type of an instance to either cluster architecture or non-cluster architecture. To change the architecture type and downgrade an instance, you must change the architecture type before you downgrade the specifications. For example, to change an 8 GB standard instance to a 4 GB cluster instance, you must first change the instance type of the standard instance to a cluster instance. Then, downgrade the capacity of the cluster instance from 8 GB to 4 GB.

Notice After you change a non-cluster instance to a cluster instance or change a cluster instance to a non-cluster instance, the original alert settings become invalid. You must reconfigure the alert settings. For more information, see Alert settings.

The duration of a specification change depends on various factors such as network conditions, task queue size, and data volume. We recommend that you change specifications during off-peak hours and make sure that your applications have automatic reconnection mechanisms.

Pricing

For more information, see Instance scaling.

Impacts

  • During the specification change, the instance may be disconnected for less than 30 seconds once or twice.
    Note For the Luttece client, the instance may be disconnected for 2 to 10 minutes.
  • To accelerate the synchronization of incremental data between the new instance and original instance and avoid data dual-writing caused by DNS cache, the instance becomes read-only for less than 1 minute during the specifications change. This ensures data consistency between the new instance and original instance.
  • When you change specifications, if you set Switching Time to Switching during serviceable time, the instance will be changed when the time arrives. For more information, see Set a maintenance window.

Procedure (pay-as-you-go)

  1. Log on to the ApsaraDB for Redis console.
  2. In the top navigation bar, select the region where the target instance is located.
  3. On the Instances page, click the Instance ID of the target instance.
  4. In the upper-right corner of the page, click Change Configurations .
  5. On the Update page, modify the specifications and click Activate.

    If the specifications are changed, a message appears to notify you that the operation is successful. Then, this pay-as-you-go instance is billed based on the new specifications in the current billing cycle.

Procedure (subscription)

  1. Log on to the ApsaraDB for Redis console.
  2. In the top navigation bar, select the region where the target instance is located.
  3. On the Instances page, click the Instance ID of the target instance.
  4. In the upper-right corner of the page, click Upgrade or Downgrade.
    Note Higher specifications are charged more than lower specifications. For more information, see Upgrade and Downgrade. For example, the price of an 8 GB read/write splitting instance with five read replicas is higher than that of a 16 GB cluster instance. If you want to change a 16 GB cluster instance to an 8 GB read/write splitting instance with five read replicas, you must upgrade the instance.
  5. On the Update page, specify the specifications and click Pay.
  6. Complete the payment.

Related API operations

ModifyInstanceSpec