This document describes how to elastically scale an instance in the TencentDB for Redis console to better optimize resource utilization and costs in real time.
For instance specifications adjustment, an instance can be scaled quickly in the console without having to stop the services. No operations are required at your side.
The instance will be billed hourly based on the new specification on the next hour under tier 1, and fees will be settled on each hour. The pay-as-you-go billing mode adopts tiered pricing in three tiers as detailed in Billing Overview. For tiered prices, see Pricing.
Note:
- After the configuration is adjusted, the instance will be charged at the price of the new configuration.
- To expand the capacity of a Memory Edition instance in standard architecture, if the remaining available capacity of the physical machine is insufficient, a migration will occur, which will not affect your access to the instance. However, if the instance is running on Redis 2.8, a momentary disconnection will occur after the migration is completed, so we recommend that your business have a reconnection mechanism.
- As the maximum capacity of a Memory Edition instance in standard architecture is 64 GB, you cannot expand its capacity beyond that limit.
- To avoid failure in capacity reduction, the capacity after reduction must be at least 1.3 times the amount of existing data. After the capacity reduction, you will receive an automatic refund.
Select Configure > Expand Node to enter the TencentDB for Redis Configuration Changes page and select the desired node capacity.
Select Configure > Reduce Node to enter the TencentDB for Redis Configuration Changes page and select the desired node capacity. The parameters for node reduction are similar to those for node expansion. Capacity After Expansion refers to the capacity specification of each shard after reduction. The instance capacity after reduction must be at least 1.3 times the used capacity. You should compare the capacity specification before and after reduction to check whether this requirement is met.
Parameter | Description |
---|---|
Used Capacity | Used capacity of the current instance. |
Min Memory | Minimum memory specification of the current instance required to prevent the disk space from being used up. |
Capacity After Expansion | Capacity specification per shard after scaling. |
Compare | Compare the current configuration with the new configuration, including **Shard Quantity**, **Shard Specs**, **Replica Quantity**, **Total Capacity**, **Total Connections**, and **Max Traffic**. |
Configuration Change Fee |
|
Select Configure > Add Replica to enter the TencentDB for Redis Configuration Changes page. Select the desired number of replicas in the drop-down list next to Replica Quantity. Other parameters are similar to those during node expansion. For more information on how to add replicas to a multi-AZ deployed instance, see Adding Replicas to Multi-AZ Deployed Instance.
Select Configure > Delete Replica to enter the TencentDB for Redis Configuration Changes page. Select the desired number of replicas in the drop-down list next to Replica Quantity. Other parameters are similar to those for node expansion.
Note:
- After the configuration is adjusted, the instance will be charged at the price of the new configuration.
- To avoid failure in capacity reduction, the capacity after reduction must be at least 1.3 times the amount of existing data. After the capacity reduction, you will receive an automatic refund.
- When shards are added or deleted, the system will automatically balance the slot configuration and migrate data, which may fail in rare cases. We recommend you perform such operations during off-peak hours to avoid the impact of migration on business access.
Log in to the TencentDB for Redis console.
Above the instance list on the right, select the region.
In the instance list, find the target instance.
In the Operation column, expand or reduce nodes or add or delete replicas or shards.
Select Configure > Expand Node to enter the TencentDB for Redis Configuration Changes page and select the desired node capacity per shard.
Select Configure > Reduce Node to enter the TencentDB for Redis Configuration Changes page and select the desired node capacity per shard. The parameters for node reduction are similar to those for node expansion. Shard Size refers to the capacity specification of each shard after reduction. The instance capacity after reduction must be at least 1.3 times the used capacity. You should compare the capacity specification before and after reduction to check whether this requirement is met.
Parameter | Description |
---|---|
Used Capacity | Used capacity of the current cluster instance. |
Min Memory | Minimum memory specification per shard of the current cluster instance required to prevent the disk space from being used up. |
Shard Size | Capacity specification per shard after scaling. |
Compare | Compare the current configuration with the new configuration, including **Shard Quantity**, **Shard Specs**, **Replica Quantity**, **Total Capacity**, **Total Connections**, and **Max Traffic**. |
Configuration Change Fee |
|
Select Configure > Add Replica to enter the TencentDB for Redis Configuration Changes page. Select the desired number of replicas in the drop-down list next to Replica Quantity. Other parameters are similar to those for node expansion. For more information on how to add replicas to a multi-AZ deployed instance, see Adding Replicas to Multi-AZ Deployed Instance.
Select Configure > Delete Replica to enter the TencentDB for Redis Configuration Changes page. Select the desired number of replicas in the drop-down list next to Replica Quantity. Other parameters are similar to those for node expansion.
Select Configure > Add Shard to enter the TencentDB for Redis Configuration Changes page. Select the desired number of shards in the drop-down list next to Shard Quantity. Other parameters are similar to those for node expansion.
Select Configure > Delete Shard to enter the TencentDB for Redis Configuration Changes page. Select the desired number of shards in the drop-down list next to Shard Quantity. Other parameters are similar to those for node expansion.
Confirm the configuration adjustment and click OK.
Return to the instance list. After the Instance Status changes to Running, the instance can be used normally.
API | Description |
---|---|
UpgradeInstance | Upgrades instance configuration |
Was this page helpful?