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

Billing

For more information, see Configuration change.

Change process and impacts

Instance Change process and impact
Figure 1. Change process of instances that use local disks
Change process of instances that use local disks
  • The cluster architecture imposes requirements on Lua scripts. After you change an instance to the cluster architecture, the Lua scripts may be lost because 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 experience one or two transient connections that last for less than 30 seconds. For Lettuce 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 dual write caused by the Domain Name System (DNS) cache, the instance becomes read-only for less than 1 minute during the configuration change. This ensures data consistency between the new and original instances.
  • To ensure higher performance and stability, the system updates the minor version of an instance to the latest version during the configuration change.

During the configuration change, ApsaraDB for Redis migrates slots to the newly added data shards. This can help achieve imperceptible scaling. During this process, the latency remains under 100 milliseconds.

Note For more information about instances that use local disks and those that use cloud disks, see Comparison between ApsaraDB for Redis instances that use local disks and those that use cloud disks.

Limits

Instance Limits
Instances that use local disks
  • Before you change a non-cluster instance into a cluster instance, you must evaluate how the command limits of cluster instances affect your workloads. For more information, see Limits on commands supported by cluster instances.
  • If you change the architecture of an instance (such as from standard to cluster), the existing alert settings become invalid and the data flashback feature is disabled.
  • If a private endpoint is allocated to an ApsaraDB for Redis cluster instance and you want to change the number of shards for the instance, you can only double the current number of shards. For more information about private endpoints, see Enable the direct connection mode. For example, if the original 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:
Cluster instances that use cloud disks
  • You can change the quantity but not the specifications of data shards.
  • An instance can contain 2 to 256 shards. You can add or reduce up to 64 shards each time.
  • The specifications of the shards that you want to add are the same as those of existing shards and cannot be modified.

For more information, see Adjust the number of shards for an ApsaraDB for Redis instance.

Child instance in a distributed instance
  • You cannot change the architecture of a child instance (such as from cluster to standard).
  • To change the configurations 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 a child instance. For example, if the original 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 scale the instance from two shards to four shards and then scale the instance from four shards to eight shards.

When you downgrade the configurations of an instance, note that 90% of the memory capacity of the new instance is greater than the amount of occupied memory of the original instance. Otherwise, the instance cannot be downgraded. For example, assume that you have a performance-enhanced master-replica instance with 8 GB of memory and that 3 GB of the instance memory is occupied. You can change the instance into a performance-enhanced master-replica instance that has 4 GB of memory.

Manually change the configurations of an instance

  1. Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance is deployed. Then, find the instance and click its ID.
  2. Perform the corresponding operations described in the following table based on the billing method of your instance.
    Billing method Procedure
    Pay-as-you-go
    1. In the upper-right corner of the page, click Change Configurations .
    2. On the Upgrade/Downgrade page, make required configuration changes and click Buy Now.
    Subscription
    1. In the upper-right corner of the page, click Upgrade.
    2. On the Upgrade/Downgrade page, make required configuration changes and click Buy Now.
    Note
    • If you want to change a non-cluster instance into a cluster instance, or change a cluster instance into another cluster instance, take note of the following items:
      • You must read and confirm the related limits of cluster instances. For more information about these limits, see Limits on commands supported by cluster instances.
      • If the original instance contains Lua scripts, back up the Lua scripts in advance. Then, select Force Upgrade during the configuration change to delete the Lua scripts of the original instance.
    • 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.
  3. Pay for the order.

Related API operations

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