ApsaraDB for Redis allows you to upgrade or downgrade an instance based on your business requirements to optimize resource usage and data management.
Change process and impacts
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. For more information about the process, impacts, and specific operations of a configuration change, see Change the configurations of an instance.
Pay-as-you-go instances
A pay-as-you-go instance is billed based on the configurations that are used when a billing order is generated.
Subscription instances
You can change the configurations of a subscription instance before or after the instance expires. You can upgrade or downgrade an instance. Higher specifications cost more than lower specifications. 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 change a 16 GB cluster instance to an 8 GB read/write splitting instance with five read replicas, you must upgrade the instance.
You cannot change the configurations if an unpaid renewal order exists in your account.
Action | Billing |
Upgrade | Total fees for upgrading an instance = (Daily fees of the instance after upgrade - Daily fees of the instance before upgrade) × (Number of days between the subscription expiration date and the upgrade date) |
Downgrade | Downgrade refunds = (Daily fees of the instance before the downgrade - Daily fees of the instance after the downgrade) × (Number of days between the subscription expiration date and the downgrade date) For more information about downgrade refunds, see Rules for unsubscribing from resources. |
Change instances between editions
You can change an ApsaraDB for Redis instance that uses local disks from Community Edition to Enhanced Edition (Tair).
You cannot change an ApsaraDB for Redis instance from Enhanced Edition (Tair) to Community Edition.
FAQ
Q: Can I change the configurations of an instance across storage types?
A: No, you cannot change the configurations of an instance across storage types.
Q: Can I upgrade only the CPU resources for an instance?
A: No, you cannot upgrade only the CPU or memory resources for your ApsaraDB for Redis instance. You can upgrade the instance specifications or change the architecture of the instance to improve the overall performance of the instance. For more information, see Overview.
Q: Can I upgrade a local disk-based instance to a cloud disk-based instance?
A: No, you cannot upgrade a local disk-based instance to a cloud disk-based instance. You can purchase a cloud disk-based instance and migrate the data of a local disk-based instance to the cloud disk-based instance. For more information, see Migrate data between ApsaraDB for Redis instances.
Q: How do I implement imperceptible scaling for an instance?
A: Configuration change may cause one or two transient connections that each lasts 30 seconds or less. You can implement imperceptible scaling for a cloud disk-based ApsaraDB for Redis Enhanced Edition (Tair) cluster instance. For more information, see Imperceptible scaling.