ApsaraDB for Redis allows you to change the configurations of instances. You can change configurations such as the architecture and specifications of an instance to meet different performance and capacity requirements.
For more information, see Configuration changes.
Change processes and impacts
Change process and impact
During the configuration change, ApsaraDB for Redis migrates slots, for example, to the newly added data shards. Redis performs data migration in the background, allowing for imperceptible scaling without blocking business requests. During this process, the latency remains within 100 milliseconds.
After you change the configurations of an instance, the instance information that includes the instance ID, endpoints, data, whitelists, and existing accounts and their corresponding passwords does not change.
Local disk-based instance
Cloud disk-based instance that uses the cluster architecture
For more information, see Adjust the number of shards for an ApsaraDB for Redis cloud-native instance.
Child instance in a distributed instance
When you downgrade the configurations of an instance, note that 80% of the memory capacity of the new instance must be greater than the amount of occupied memory in the original instance. Otherwise, the instance cannot be downgraded. For example, if the original instance is a standard DRAM-based instance that has a storage capacity of 8 GB and has 2 GB used, you can downgrade the instance to a standard DRAM-based instance that has a storage capacity of 4 GB.
Manually change the configurations of an instance
- 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.
Perform the corresponding operations described in the following table based on the billing method of your instance.
In the upper-right corner of the page, click Change Configurations .
On the Upgrade/Downgrade page, make the required configuration changes and click Buy Now.
In the upper-right corner of the page, click Upgrade.
On the Upgrade/Downgrade page, make required configuration changes and click Buy Now.
If large keys exist in the original instance, the configuration change may fail.
In this case, we recommend that you identify and delete large keys from the instance before you perform the configuration change. For more information about how to identify large keys, see Use the offline key analysis feature.
If you want to change a non-cluster instance to a cluster instance, or change the instance type of a cluster instance without changing its architecture, 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 and read/write splitting instances.
If the original instance contains Lua scripts, back up the Lua scripts in advance and select Force Upgrade during the configuration change. This way, you can complete the configuration change.
If you select Force Upgrade, the Lua scripts are deleted from the original instance after the configuration change.
When you change the configurations of an instance, we recommend that you set the Switching Time parameter to Switch Within Maintenance Window. In this case, the instance configurations are changed in the next maintenance window. For more information, see Set a maintenance window.
Complete the payment.
Related API operations
Changes the configurations of an ApsaraDB for Redis instance.