tencent cloud

All product documents
TencentDB for Redis®
Upgrading Instance Architecture
Last updated: 2024-11-05 10:10:15
Upgrading Instance Architecture
Last updated: 2024-11-05 10:10:15

Overview

TencentDB for Redis® supports standard architecture and cluster architecture. To help you process ever-growing business data, it allows you to upgrade from standard architecture to cluster architecture if the performance and capacity of standard architecture are insufficient.

Upgrade description

For Redis 4.0 or later, a standard architecture instance can be upgraded to a cluster architecture instance on the same version; for example, you can upgrade from Redis 4.0 Standard Architecture to Redis 4.0 Cluster Architecture.
Cross-version architecture upgrade is not supported; for example, you cannot upgrade from Redis 4.0 Standard Architecture to Redis 5.0 Cluster Architecture.
The architecture of Redis 2.8 cannot be upgraded.
Cluster architecture cannot be downgraded to standard architecture.
Cross-AZ architecture upgrade is not supported.
Cluster architecture upgrade is not supported for pay-as-you-go instances.
After standard architecture is upgraded to cluster architecture, fees will be charged based on cluster architecture and thus get increased. For more information, see Pricing.

How upgrade works

Redis standard architecture can be directly upgraded to cluster architecture (single-shard) in three minutes with no data migration required.
In Redis 4.0 or later, if standard architecture is upgraded to cluster architecture, only the runtime mode of the instance will change from having no slot limit to having one, but no data migration will occur.

Upgrade preparations (compatibility check)

To avoid business failures caused by compatibility problems during migration to cluster architecture, check the compatibility before the upgrade:
Cluster architecture stores data in a distributed manner, and its biggest difference from standard architecture lies in whether a single command supports multikey access. For the cluster architecture, commands can be categorized into supported, partially supported, and unsupported. For the complete list of compatible commands, see Overview.
For more information about compatibility check, see Check on Migration from Standard Architecture to Cluster Architecture.

Upgrade impact

Generally, upgrade can be completed in three minutes.
During the upgrade, existing connections will be closed momentarily; therefore, your business should have a reconnection mechanism.

Directions

2. Above the instance list on the right, select the region.
3. In the instance list, find the target instance.
4. Click the instance ID to enter the Instance Details page.
5. In the Specs Info section on the Instance Details page, click Upgrade Architecture after Architecture.

6. In the pop-up window, configure the upgrade parameters according to the table below.

Parameter
Description
Instance ID
ID of the instance to be upgraded.
Instance Name
Name of the instance to be upgraded.
Compatible Version
The current compatible Redis version of the instance to be upgraded.
Architecture
Architecture information of the instance to be upgraded.
Memory
Memory size of the instance to be upgraded.
Architecture
Select the target architecture in the drop-down list. Currently, the standard architecture can be upgraded to the cluster architecture, but the cluster architecture cannot be downgraded to the standard architecture.
Preview New Specs
Preview information of the instance specifications after upgrade.
Switch Time
Switch Now: The switch will be performed immediately.
Switch in Maintenance Time: The switch will be performed during the instance maintenance time. You can modify the Maintenance Time on the instance details page. We recommend that you switch during off-peak hours.
Total Fees
Fees after the architecture upgrade.
Pay-as-you-go: The hourly unit price after instance architecture upgrade. You can click Billing Details to view the billable items and billing formula and confirm the fees.
Monthly subscription: The total fees of the instance before it expires after the architecture is upgraded.
7. There is a command compatibility risk when upgrading to the cluster architecture edition. Click Compatibility Description Document, confirm the compatibility risk, click There is a command compatibility risk when upgrading to the cluster architecture edition (Compatibility Description Document), I've confirmed the compatibility risk and agreed to upgrade., and click OK to proceed with the upgrade.
8. On the order page, confirm the order information and the fees to be paid, and hover over

to view the detailed calculation of the fees. After confirming that everything is correct, click Submit Order. Make the payment and return to the instance list. After the Instance Status changes to Running, you can see that the instance architecture has been upgraded to cluster architecture in the instance list or instance details.

Related APIs

API
Description
Upgrades the instance architecture
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon