ApsaraDB for Redis allows you to change the configurations of instances. You can change the configurations such as the architecture and specifications to meet different performance and capacity requirements.

Pricing

For more information, see Configuration change.

Change process and impact

Figure 1. Change process
Change process
  • The cluster architecture imposes requirements on Lua scripts. After you change an instance to the cluster architecture, the Lua scripts may be lost because the script content does not meet the requirements. You must back up the Lua scripts in advance. For more information, see Limits on commands supported by cluster instances.
  • If you change the configurations of an instance, the instance may be disconnected for no more than 30 seconds for one or two times. For Luttece clients, the instance may be disconnected for 2 to 10 minutes.
    Note We recommend that you set the Switching Time parameter to Switch Within Maintenance Window when you change the configurations of an instance. In this case, the instance configurations are changed and transient connections occur in the next maintenance window.
  • To synchronize incremental data from the original instance to the new instance and prevent doublewrite caused by the DNS cache, the instance becomes read-only for less than 1 minute during the configuration change. This ensures data consistency between the new instance and the original instance.
  • To ensure higher performance and stability, the system updates the minor version of an instance to the latest version during the configuration change.

Limits

Instance type Limit
Regular ApsaraDB for Redis instance
  • Before you change a non-cluster instance to a cluster instance, you must evaluate how the command limits of the cluster instance affect your workloads. For more information, see Limits on commands supported by cluster instances.
  • If you change the architecture of an instance, the existing alert settings become invalid. For example, you may change the architecture from standard to cluster. In this case, you must reconfigure the alert settings. For more information, see Alert settings.
  • If the direct connection endpoint is enabled for a cluster instance of ApsaraDB for Redis and you want to change the number of shards, 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 only to four shards. You cannot directly scale the instance to eight shards. If you want to scale the instance from two shards to eight shards, use one of the following methods:
    • You can first scale the instance from two shards to four shards. Then, scale the instance from four shards to eight shards.
    • You can also release the direct connection endpoint. Then, you can directly scale the instance to eight shards. For more information, see Release a direction connection endpoint.
Child instance in a distributed instance
  • You cannot change the architecture of a child instance. For example, you cannot change the architecture of a child instance from cluster to standard.
  • To change the specifications of a child instance in a distributed instance, you must change the configurations of all the other child instances in the distributed instance in the same way. Otherwise, performance or capacity issues may occur.
  • You can only double the current number of shards for the child instance. For example, if the original ApsaraDB for Redis instance has two shards, you can scale the instance only to four shards. You cannot directly scale the instance to eight shards.
    Note If you want to scale the instance from two shards to eight shards, you can first scale the instance from two shards to four shards. Then, scale the instance from four shards to eight shards.

Manually change the configurations of an instance

  1. Log on to the ApsaraDB for Redis console.
  2. In the top navigation bar of the page, select the region where the instance is deployed.
  3. On the Instances page, click the ID of the instance.
  4. Perform one of the operations described in the following table based on the billing method of your instance.
    Billing method Description
    Pay-as-you-go
    1. In the upper-right corner of the page, click Change Configurations .
    2. On the Upgrade/Downgrade page, select the configurations and click Buy Now.
    Subscription
    1. In the upper-right corner of the page, click Upgrade or Downgrade.
    2. On the Upgrade/Downgrade page, select the configurations and click Pay.
      Note If you change the architecture to cluster, you must read and confirm the limits of the cluster architecture. For more information, see Limits on commands supported by cluster instances. Then, select Force Upgrade to complete the configuration change.
    Note We recommend that you set the Switching Time parameter to Switch Within Maintenance Window when you change the configurations of an instance. In this case, the instance configurations are changed in the next maintenance window.
  5. Complete the payment.

Related operations

Operation Description
ModifyInstanceSpec Changes the configurations of an ApsaraDB for Redis instance.