Tair (Redis OSS-compatible) lets you change instance configurations on demand, including the instance architecture, shard specifications, and number of shards. This helps you improve resource utilization and optimize costs. This topic describes the fees for instance upgrades and the refund policy for instance downgrades.
Pay-as-you-go instances
If you change the configurations of a pay-as-you-go instance, you are charged based on the instance configurations at the time of order creation.
You can pay for pay-as-you-go instances after you use the instances. This billing method does not involve refunds upon configuration downgrade.
Subscription configuration changes
You can change the configurations of a subscription instance before or after it expires. If the new configuration costs more than the current one, it is an upgrade. Otherwise, it is a downgrade. For example, an 8 GB read/write splitting instance with five read-only nodes costs more than a 16 GB cluster instance. Changing from the 16 GB instance to the 8 GB instance is considered an upgrade.
Upgrade/Downgrade Methods | Billing rule |
Upgrade | Instance upgrade fee = (Original price for the remaining validity period of the instance after upgrade - Original price for the remaining validity period of the instance before upgrade) × Discount for the remaining validity period of the instance
|
Downgrade | Refundable amount for the downgrade of resource specifications = Online refundable amount × Price difference ratio between new and original orders. If you request refunds for multiple orders, the refundable amount for each order is calculated and summed up. For more information about the online refund amount and the price difference ratio between the new and original configurations, see Refund rules for the international site. |
Changes between editions
Redis Open-Source Edition classic instances can be upgraded to Tair (Enterprise Edition) instances.
Tair (Enterprise Edition) instances cannot be changed to Redis Open-Source Edition instances.
FAQ
Refund destinations
Refunds are returned to the original payment account after you confirm the unsubscription.
Payment method | Refund destination |
Credit card | The refund is returned to your credit card account if you request a refund in five months (150 days) after you complete payment. The refund is returned to your Alibaba Cloud account if you request a refund five months after you complete the payment. |
PayPal | The refund is returned to your PayPal account if you request a refund in six months (180 days) after you complete payment. The refund is returned to your Alibaba Cloud account if you request a refund six months after you complete payment. |
Paytm | The refund is returned to your Paytm account if you request a refund in one year (365 days) after you complete payment. The refund is returned to your Alibaba Cloud account if you request a refund one year after you complete payment. |
Alibaba Cloud account balance | Alibaba Cloud account balance |
Refund arrival time
After you confirm the unsubscription, the refund time will be affected by the processing speed. Refunds are issued in 30 business days.
References
To change the memory size of shards, architecture, number of shards, or number of read-only nodes for a classic deployment instance, see Change instance configurations.
To increase or decrease the number of shards for a cloud-native cluster instance, see Adjust the number of shards for a cluster.
To enable read/write splitting for a cloud-native instance, see Enable read/write splitting.