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 impact
For more information about the process, impact, and operation methods of a configuration change, see Modify the configurations of an instance.
A pay-as-you-go instance is billed based on the configurations that are used when a billing order is generated.
You can change the configurations of a subscription instance before or after the instance expires. You can upgrade or downgrade an instance. Higher specifications are charged more than lower specifications. For example, the price of an 8 GB read/write splitting instance with five read replicas is higher than the price of a 16 GB cluster instance. If you change a 16 GB cluster instance to an 8 GB read/write splitting instance with five read replicas, you are upgrading the instance.
|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 downgrade - Daily fee of the instance after downgrade) × (Number of days between the subscription expiration date and the downgrade date)|
If the remaining days before service expiration are less than 365 days, you are charged based on the monthly subscription price. If the remaining days are greater than or equal to 365 days, you are charged based on the annual subscription price.
Change instances between editions
- You can change an ApsaraDB for Redis instance from Community Edition to Enhanced Edition (Tair).
- You cannot change an ApsaraDB for Redis instance from Enhanced Edition (Tair) to Community Edition.
Change ApsaraDB for Redis Enhanced Edition (Tair) instances between series
You cannot change instances between performance-enhanced series and hybrid-storage series.