Tair (Redis OSS-compatible) lets you change instance configurations on demand—including the instance architecture, shard specifications, and number of shards—to improve resource utilization and optimize costs.
This topic describes the fees for upgrades and the refund policy for downgrades.
Pay-as-you-go instances
For pay-as-you-go instances, charges are based on the instance configuration at the time of order creation. Because pay-as-you-go billing works on a post-usage model, no refunds apply when you downgrade the configuration.
Subscription instances
You can change the configuration of a subscription instance at any time, whether before or after it expires. A change is classified as an upgrade if the new configuration costs more than the current one, or a downgrade if it costs less.
Cost—not raw specs—determines whether a change is an upgrade or downgrade. For example, an 8 GB read/write splitting instance with five read-only nodes costs more than a 16 GB cluster instance. Switching from the 16 GB cluster to that 8 GB read/write splitting instance is an upgrade, not a downgrade.
Upgrade fees
| Method | Billing rule |
|---|---|
| Upgrade | Instance upgrade fee = (Original price for the remaining validity period after upgrade − Original price for the remaining validity period before upgrade) × Discount for the remaining validity period |
Where:
Original price for the remaining validity period after upgrade = Unit price after upgrade × Remaining validity period
Original price for the remaining validity period before upgrade = Unit price before upgrade × Remaining validity period
Downgrade refunds
Refundable amount = Online refundable amount × Price difference ratio between the new and original orders
If you downgrade multiple orders, the refundable amount for each order is calculated separately and then summed. For details on how the online refundable amount and the price difference ratio are calculated, see Refund rules for the international site
Edition changes
The following restrictions apply when changing between editions:
Redis Open-Source Edition classic instances can be upgraded to Redis Enhanced Edition (Tair) instances.
Redis Enhanced Edition (Tair) instances cannot be changed to Redis Open-Source Edition instances.
FAQ
Refund destinations
Refunds are generally returned to the original payment method.
Payment method | Refund destination |
Debit or credit card | If you request a refund within five months (150 days) after you complete payment, the refund is returned to your debit or credit card account. Otherwise, the refund is returned to your Alibaba Cloud account. |
PayPal | If you request a refund within six months (180 days) after you complete payment, the refund is returned to your PayPal account. Otherwise, the refund is returned to your Alibaba Cloud account. |
Paytm | If you request a refund within within one year (365 days) after you complete payment, the refund is returned to your Paytm account. Otherwise, the refund is returned to your Alibaba Cloud account. |
Alibaba Cloud account balance | Alibaba Cloud account balance. |
Refund arrival time
After you successfully unsubscribe from a product, the time it takes for the refund to arrive depends on the processing speed of the payment method. The refund is typically credited to your account within 30 business days.
Where does my refund go?
Refunds are returned to the original payment account after you confirm the unsubscription.
| Payment method | Within the time limit | After the time limit |
|---|---|---|
| Credit card | Returned to your credit card account within 5 months (150 days) of payment | Returned to your Alibaba Cloud account |
| PayPal | Returned to your PayPal account within 6 months (180 days) of payment | Returned to your Alibaba Cloud account |
| Paytm | Returned to your Paytm account within 1 year (365 days) of payment | Returned to your Alibaba Cloud account |
| Alibaba Cloud account balance | Returned to your Alibaba Cloud account balance | — |
How long does a refund take?
Refunds are issued within 30 business days after you confirm the unsubscription.
What's next
To change the memory size, 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.