TencentDB for Redis supports instance specification adjustment to enable flexible scaling. You can elastically adjust the specification of your Redis instance based on your actual business needs so as to better optimize resource utilization and costs in real time. This document describes how to modify instance specification in the TencentDB for Redis Console.
Note:
Pay-as-you-go instances cannot be scaled in currently.
Note:
- When you expand the capacity of the memory edition (standard architecture), if the remaining available capacity of the instance is insufficient to meet the capacity expansion requirements, migration will occur, which will not affect the service access. However, there will be a momentary interruption after the migration is completed, and we recommend that you implement a reconnection mechanism for your business.
- Because the memory edition (standard architecture) has a maximum capacity of 384 GB, when the capacity reaches 384 GB, it cannot be expanded any further.
- To avoid failure in capacity reduction, the capacity after reduction should be at least 1.3 times the amount of existing data. The system will refund automatically after capacity reduction.
Note:
- After the configuration is adjusted, the instance will be charged at the price of the new specification.
- To avoid failure in capacity reduction, the capacity after reduction should be at least 1.3 times the amount of existing data. The system will refund automatically after capacity reduction.
- When shards are added or deleted, the system will automatically balance the slot configuration and migrate data, which may fail in rare cases. It is recommended to perform such operations during off-peak period so as to avoid the impact of migration on business access.
Was this page helpful?