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.
Billing
If you change the configurations of a pay-as-you-go instance, you are charged based on the new specifications after the change. If you change the configurations of a subscription instance, you are charged or are refunded the difference in cost based on whether you upgrade or downgrade the configurations.
For more information about the billing rules for configuration changes and the refund for configuration downgrade, see Configuration changes.
Change process
Impacts of configuration changes
Local disk-based and cloud disk-based standard instances
If you change the configurations of an instance, the instance may experience one or two transient connections that each lasts up to 30 seconds.
To synchronize incremental data from the original instance to the new instance and prevent dual writes caused by the Domain Name System (DNS) cache, the instance becomes read-only for up to 1 minute during the configuration change.
To ensure higher performance and stability, the system updates the minor version of the instance to the latest version during the configuration change.
If you change the architecture of an instance, the following impacts may occur:
The existing alert settings become invalid. To continue using the alert feature, you must reconfigure alert settings. For more information, see Alert settings.
The data flashback feature is disabled. To continue using the feature, enable the feature. For more information, see Use data flashback to restore data by point in time.
The cluster architecture imposes requirements on Lua scripts. After you change a non-cluster instance to a cluster instance, the Lua scripts may be lost because the script content does not meet the requirements. Make sure to back up the Lua scripts in advance. For more information, see Limits on commands supported by cluster instances and read/write splitting instances.
Cluster instances and read/write splitting instances do not support specific commands. Before you change a non-cluster instance to 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 and read/write splitting instances.
Cloud disk-based cluster instances
If you change the specifications of a shard, a master-replica switchover may occur. During the switchover, the shard may experience a transient connection.
Limits
Feature matrix for configuration changes
The configuration change options that are supported on the Change Configurations page (Upgrade or Downgrade page for subscription instances) vary based on the deployment method and architecture.
The following list describes the symbols that are used in the following tables:
✔️ indicates that you can perform operations on the Change Configurations page.
⭕️ indicates that you cannot perform operations on the Change Configurations page. For specific operation methods, see the note below the table.
❌ indicates that this type of configuration change is not supported.
➖ indicates that this type of configuration change is not involved.
Deployment type/Change option | Switch to the cluster architecture | Switch to the read/write splitting architecture | Switch to the standard architecture | Change shard specifications | Change the number of shards | Change the number of read replicas |
Classic deployment | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
Cloud-native standard architecture | ✔️ | ⭕️1 | ➖ | ✔️ | ➖ | ➖ |
Cloud-native cluster architecture | ➖ | ⭕️2 | ✔️3 | ✔️ | ⭕️4 | ➖ |
Cloud-native read/write splitting architecture | ⭕️5 | ➖ | ⭕️6 | ✔️ | ➖ | ⭕️7 |
1To change the architecture of an instance from the cloud-native standard architecture to the read/write splitting architecture, enable read/write splitting for the instance on the Read/Write Splitting Settings page. For more information, see Enable read/write splitting.
2To change the architecture of an instance from the cloud-native cluster architecture to the read/write splitting architecture, change the instance to a standard instance, and then enable read/write splitting for the instance on the Read/Write Splitting Settings page.
3To change the architecture of an instance from the cloud-native cluster architecture to the standard architecture, the instance must run in proxy mode. The direct connection mode is not supported.
4To change the number of shards for a cloud-native cluster instance, add or remove shards. For more information, see Adjust the number of shards for an instance.
5To change the architecture of an instance from the cloud-native read/write splitting architecture to the cluster architecture, disable read/write splitting and then change the architecture on the Change Configurations page.
6To change the architecture of an instance from the cloud-native read/write splitting architecture to the standard architecture, disable read/write splitting on the Read/Write Splitting Settings page. For more information, see Enable read/write splitting.
7To change the number of read replicas for a cloud-native read/write splitting instance, increase or decrease the number of read replicas on the Read/Write Splitting Settings page. For more information, see Enable read/write splitting.
Procedure
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 that you want to manage resides. Then, find the instance and click the instance ID.
For a pay-as-you-go instance, click Change Configurations in the upper-right corner of the page. For a subscription instance, click Upgrade in the upper-right corner of the page.
On the Upgrade/Downgrade page, make required configuration changes and click Buy Now.
ImportantWhen 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.
FAQ
What causes a configuration change to fail?
Does the endpoint of an instance change after a configuration change? Do I need to modify the application code?
Can I change the configurations of my ApsaraDB for Redis Enhanced Edition (Tair) instance across storage types?
Can I separately improve the CPU performance of an instance?
Can I directly upgrade a local disk-based instance to a cloud disk-based instance?
How do I change a cluster instance to a standard instance?
How do I change a high-availability master-replica instance to a standalone instance?
Do I need to suspend read and write operations when I change the configurations of an instance?
When I change a standard instance to a cluster instance or adjust the number of shards for a cluster instance, is data automatically migrated to each shard?
How long does it take to perform a configuration change?
Does a configuration change cause data loss?
Why is the instance in the Changing Configuration state after I set the switchover time to Switch Within Maintenance Window and submit a configuration change request?
Related API operations
API operation | Description |
Changes the configurations of an ApsaraDB for Redis instance. |