Configuration changes
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
For more information about the unit price of the new configuration, the unit price of the original configuration, and the remaining duration, see Upgrade details.
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
Edition changes
The following edition change paths are supported:
Classic Redis Open-Source Edition → Classic Tair (Enterprise Edition)
Cloud-native Redis Open-Source Edition → Cloud-native Tair (Enterprise Edition)
Classic Redis Open-Source Edition → Cloud-native Redis Open-Source Edition (cross-architecture)
Classic Tair (Enterprise Edition) → Cloud-native Tair (Enterprise Edition) (cross-architecture)
Tair (Enterprise Edition) instances cannot be changed to Redis Open-Source Edition instances.
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.