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 information

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

Notice
  • Before you switch to a cluster instance, you must evaluate the impacts that are caused on your workloads by the command limits of the cluster instance. For more information, see Limits on the commands supported by cluster instances.
  • After you change the architecture type of an 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 multiple factors such as network conditions, task queue size, and data volume. We recommend that you change specifications during off-peak hours. Make sure that your applications support automatic reconnections.

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 synchronize incremental data between the new instance and the original instance and avoid dual-write of data caused by DNS cache, the instance becomes read-only for less than one minute during the change. This ensures data consistency between the new instance and the original instance.
  • If you set Switching Time to Switching during serviceable time when you configure a specification change, the instance is changed in the next maintenance period. For more information, see Set a maintenance window.

Limits

If the private endpoint is enabled for a cluster instance of ApsaraDB for Redis, you can only double the current number of shards for the instance. For example, if the original ApsaraDB for Redis instance has two shards, you can scale the instance to only four shards rather than eight shards.
Note To avoid impacts from the limits, you can temporarily release the private endpoint before you scale the instance. For more information, see Release a private endpoint.

Procedure for pay-as-you-go instances

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

    If you have scaled the instance, 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 for subscription instances

  1. Log on to the ApsaraDB for Redis console.
  2. On the top of the page, select the region where the instance is deployed.
  3. On the Instances page, click the Instance ID of the 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 switch 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. Pay for the order.

Related API operations

ModifyInstanceSpec